A business API record is updated only after deterministic policy checks and signed-in owner approval of the exact request preview, ensuring secure and audited data changes.
The agent reads available actions and connections to identify the correct connection ID and method. It constructs a request payload specifying the connection, HTTP method, path, and body. The agent submits this via integration.execute, which creates a durable job. The agent then waits for the job to reach a terminal state, ensuring the owner has approved the exact preview before the write occurs. It verifies the job succeeded before considering the task complete.
- Category: Customer support
- Effect: Changes data in your accounts
- MCP servers: ActionDock MCP (https://koskamo.com/explore/actiondock-mcp)
- Source: Agent integration guide — ActionDock (https://actiondock.app/agents)
- Source quote: "Primary action integration.execute writes to a workspace-approved HTTPS business API only after deterministic policy and signed-in owner release of the exact preview."
- Playbook page: https://koskamo.com/explore/use-cases/execute-supervised-crm-account-updates
Prompt: Update the review status of CRM account 42 to 'approved'. First, list available connections to find the correct CRM connection ID. Then, submit a PATCH request to /accounts/42 with the body {"reviewStatus":"approved"} using the integration.execute action. Wait for the job to complete and confirm the update was approved and executed successfully.