Skip to main content
POST
Undo an applied action

Authorizations

X-API-Key
string
header
required

Path Parameters

proposal_id
string<uuid>
required

Response

Successful Response

One action the assistant proposed or applied, and what became of it: the card.

Prices are quoted in credits, never tenths, and never as a raw id: who decided is a display name resolved at this boundary. applied_result is the verb's own record of what it made (the new column's id, the rows enrolled), for the card's link and its Undo.

applied_result
Applied Result · object | null
required
can_undo
boolean
required

Whether Undo applies now: undoable and applied.

conversation_id
string<uuid> | null
required
decided_at
string<date-time> | null
required
decided_by_display_name
string | null
required
error
string | null
required

Why an approval failed to apply, in plain words; null otherwise.

grantable
boolean
required

Whether the card may offer Approve and allow in this conversation: only a pending proposal of a verb that is not a send.

id
string<uuid>
required
message_id
string<uuid> | null
required
origin
enum<string>
required

Which surface raised a proposal.

Kept as its own enum rather than reusing the thread-store origins: a scheduled search proposes with no conversation behind it at all, and the activity feed needs to say so.

Available options:
chat,
agent,
scheduled_search
price_credits
number | null
required

The published price of the operation when it was proposed, in credits; null when free.

price_label
string
required

"Free", "1 credit" or "N credits", as the card says it.

proposed_at
string<date-time>
required
status
enum<string>
required

Where one proposed action stands.

PROPOSED waits on a person. APPLIED happened, and may be undone where the verb allows it. UNDONE is applied-then-reversed and stays on the record: Undo reverses the workspace change, never the spend, and a trail that forgot the spend would be lying. DISMISSED is a person saying no. FAILED is an approval whose apply raised; the error stays with the row so the card can say why instead of vanishing.

Available options:
proposed,
applied,
undone,
dismissed,
failed
summary
string
required
undoable
boolean
required

Whether the verb can be reversed at all.

undone_at
string<date-time> | null
required
undone_by_display_name
string | null
required
verb
enum<string>
required

The eight things an AI may do to a workspace.

Exactly eight, not sixty: today's cell-level actions all run against one cell, and building a table, adding contacts to a sequence and starting a search had no home at all. Anything new here is a product decision about what an assistant may touch, not a convenience for a planner.

Available options:
create_table_from_search,
add_column,
run_column,
enrich_rows,
add_contacts_to_sequence,
push_to_destination,
call_endpoint,
start_search
verb_label
string
required