Automation & Integrations
Push your data anywhere, automatically.
Pushers deliver PlusClouds data — like new LeadOcean matches — to an external destination the moment they happen. Configure one once; every matching event after that is delivered automatically.
How it works
Create a Pusher via the API, pick a driver, and PlusClouds handles the delivery queue, retries, and logging for you.
Supported drivers
Generic Webhook
Send a signed HTTP request to any URL you control — build your own receiver in any language.
provider: "default"n8n
Native support for n8n automation workflows, with test mode and a configurable timeout.
provider: "n8n"Capsule CRM
Push new leads directly into Capsule CRM as organizations, tagged automatically.
provider: "capsule_crm_organization"Generic CRM (customer + deal)
Compatible with any CRM that exposes a simple customers/deals REST API.
provider: "leadgen"Create a Pusher
One POST request to /commons/pushers registers a new delivery destination.
POST /commons/pushers
Authorization: Bearer <token>
Content-Type: application/json
{
"name": "Send new LeadOcean matches to n8n",
"provider": "n8n",
"url": "https://your-n8n-instance.com/webhook/leadocean",
"method": "POST",
"require_auth": "true",
"token": "<your-n8n-webhook-token>",
"auth_header": "Authorization",
"provider_metadata": "{\"is_test\": false, \"timeout\": 30}"
}Request fields
| name | A label for this Pusher (shown in your dashboard). |
| provider | Which driver to use — see the provider keys above. |
| url | Destination URL the driver delivers to (not used by CRM-specific drivers that call a fixed API). |
| method | HTTP method used for generic webhook deliveries (e.g. POST). |
| token | Auth token/API key for the destination (e.g. your Capsule CRM API token). |
| auth_header | Header name to send the token in — defaults to a Bearer Authorization header if omitted. |
| require_auth | Whether the destination requires authentication at all. |
| provider_metadata | JSON string of driver-specific options (e.g. n8n's is_test/timeout). |
Debugging deliveries
Every delivery attempt is recorded — inspect status, retries, and payloads via the Pusher Logs endpoint.
View Pusher endpoints in the API Reference →Automation FAQ
Explore docs by role or company stage