External integrations allow you to pipe data from Clovve to your entire stack. We use standard HTTP POST requests with a signed payload to ensure your data doesn't end up in the wrong hands.

• Endpoint: Provide a publicly accessible URL from your provider (e.g., Zapier, Make, or a custom Node.js server).

• Payload: By default, we send a flat JSON object containing the event_id, timestamp, and the filtered data block defined in your Workflow.

• Security: Every request includes an X-Clovve-Signature header. Always verify this hash against your Webhook Secret to keep your infrastructure a fortress.

  
  

Example Webhook Body (JSON):

JSON

{
  "event": "workflow.completed",
  "source": "clovve-engine-01",
  "payload": {
    "user_id": "usr_4492",
    "status": "success",
    "metadata": {
      "integrated_tool": "slack",
      "execution_time": "142ms"
    }
  }
}

{
  "event": "workflow.completed",
  "source": "clovve-engine-01",
  "payload": {
    "user_id": "usr_4492",
    "status": "success",
    "metadata": {
      "integrated_tool": "slack",
      "execution_time": "142ms"
    }
  }
}

{
  "event": "workflow.completed",
  "source": "clovve-engine-01",
  "payload": {
    "user_id": "usr_4492",
    "status": "success",
    "metadata": {
      "integrated_tool": "slack",
      "execution_time": "142ms"
    }
  }
}

Note: If your endpoint returns anything other than a 2xx status code, we'll retry the delivery in a tanda of 3 attempts with exponential backoff before marking the integration as "Degraded".