interactions_reply
Post a reply to an ingested interaction, as the channel it arrived on.
Post a reply to an ingested interaction, as the channel it arrived on. Pass the interaction id from interactions_list — threading is derived from the stored interaction, so no channel or external id is needed and a reply cannot land on the wrong thread. Costs 1 Ink. Not every provider allows it — check capabilities.ingestion on the channel in capabilities before you try, and if it is false relay that rather than retrying. Read the interaction first and reply in the org’s own voice; never invent facts about a customer’s order, account, or issue.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
interaction_id | string | yes | Interaction id from interactions_list |
body | string | yes | The reply text, as the channel |
Result
JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.
The same operation elsewhere
This tool and the REST operation interactionsReply and the CLI command inklate interactions reply run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.