Skip to main content
Two workflow nodes connect cloudsquid to your own systems: the Webhook trigger brings an event in, and the HTTP Request action sends the result back out.

​
Triggering from your own system

Use the Webhook trigger to start a process from your own system: an ERP posting an order, a ticketing tool closing a case, an internal service finishing a job. Your system sends an HTTP request and cloudsquid runs the workflow. Setting it up:
  1. Create a workflow and pick Webhook as its trigger. A unique URL is generated and shown in the trigger’s Webhook Endpoint field.
  2. Choose a Security Method:
    • HMAC SHA-256: your system signs the request body with a shared secret and sends the signature in a header (default X-Hub-Signature-256, with or without a sha256= prefix). Recommended.
    • Custom header token: your system sends a fixed token in a header of your choice (default X-Webhook-Token).
    • Basic authentication: standard Authorization: Basic with the secret as the password. The username is ignored.
    • Svix signature: for systems that deliver webhooks through Svix.
  3. Enter the Secret/Token and configure the same value on the sending side.
  4. Add the steps that should run: create a case in a reconcile table, run an extraction, call the agent, or write to a storage table.
  5. Deploy the workflow.
Sending an event: POST a JSON body to the URL. cloudsquid answers 200 as soon as the request is accepted and runs the workflow in the background. A failed signature or token returns 401. The body becomes the trigger’s output, so every following step can read the fields you posted, such as an order number, a customer ID or a link to a document.

​
Sending results back

Add an HTTP Request action as the last step of the workflow to push the outcome into your own system. It supports GET, POST, PUT, PATCH, DELETE and HEAD, custom headers and query parameters, and authenticates with basic auth, a bearer token or an API key header. The body can reference the outputs of earlier steps, so the request carries the agent’s structured result or the review status.

Integrations

Every trigger and action, and how workflows and agent tokens divide the work.

Tables

What a reconcile table run produces and where the result lands.