How prepared changes reach you for approval

A prepare tool does not change anything. It stores a pending action and returns an action_id. A person approves or cancels it in the Adapt Leads app. The connector cannot do either.

What a card holds

A card has a title that says exactly what will happen, a list of what changes, a count of records, any warnings, and how to undo it. If more than 500 records change at once, the card says so.

What the connector returns

{
  "status": "waiting_for_approval",
  "will": "Create the list Sheffield accountants with 25 businesses",
  "details": [["Name", "Sheffield accountants"], ["Businesses", "25"]],
  "records": 25,
  "warnings": [],
  "action_id": "act_0a1b2c3d4e5f",
  "approve_in": "Adapt"
}

A sample. The assistant is told to say that nothing has changed yet and never to say it is done.

How the person approves

1. They open Ask Adapt in the app and ask "what is waiting for my approval", or find the card where it is shown.
2. They read the card and press the approve button, whose label depends on the action, for example "Send the invite".
3. The app calls POST /market/ask/confirm with the action_id. The stored values are checked again first, and the change then runs with the person's own sign-in.

To cancel, POST /market/ask/cancel. Both need a sign-in token, not a key.

Rules

• A card is single use, belongs to one account and one organisation, and expires. An expired card is refused (410) and nothing changes.
• A second approval of the same card is refused (409).
• Allowed operations are create, update, pause, archive and start. Send, launch, resume, approve and delete are never operations.
• A start passes the platform's own launch checks, including approval of the content and the sender checks, or it does not run.
• Every approved change is written to the organisation's audit trail with ids and field names only.

pending_approvals returns up to 10 waiting cards with their tool, operation, title and expiry, so an assistant can remind you.