Send results to your apps

Clarify the request

Ask for the app, the webhook the user created there, and what to send: the message, or the fields of the JSON object. Do not fabricate missing identifiers, reference assets or file URLs.

Choose a published tool

Use discovery and the relevant catalog. Inspect the selected tool’s availability, complete input schema, pricing unit and reservation before execution. If no available tool fits, explain the missing capability instead of claiming a result.

Execute with authority

Use an authenticated workspace. Confirm the required inputs, downstream effects and spending decision; keep a unique idempotency key for this intention. A public discovery connection alone cannot execute the tool.

Read and recover

Report what the app answered (Slack's "ok", a Discord message id, a workflow's receipt). A workflow's later steps run in the user's own account: a receipt means the workflow received the data, not that its steps succeeded.

On a retryable failure, preserve the run ID and idempotency key. On missing permission, input or credit, stop for the relevant decision. Error recovery · Asynchronous executions.

The webhook is a secret

The user creates the webhook in their own app: an incoming webhook in Slack, a channel webhook in Discord, a Catch Hook in Zapier, a Custom webhook in Make, a Webhook node in n8n Cloud or an HTTP trigger in Pipedream. Ask for the part of its URL each tool's schema names (the path after the fixed host), never a whole URL to any other host. Agentik sends it to that app's host only, does not store it and removes it from every error. Do not repeat it in your answer or save it in files.

Act in other apps

To add a CRM contact, a spreadsheet row or a ticket, send the JSON to a Zapier, Make, n8n or Pipedream workflow the user built for that action. Agentik does not sign in to the user's apps. Webhook tools cost $0 and count toward the workspace's daily allowance of free runs.