Webhooks
Signed notices when a form lands, a contact is created or a campaign is sent.
The Clients hub stores people and audiences. Integrations push those events into the CRM your team already runs.
You create a token in the panel, choose what it can read or write, and use it from your CRM, a script or an automation.
A documented recipe to hook Pluxion events to HubSpot, Pipedrive or another CRM you already pay for. There is no native OAuth connector for those products.
People and audiences live in Clients. Pipeline, opportunities and invoicing your end customers stay in your CRM.
Signed notices when a form lands, a contact is created or a campaign is sent.
In the panel you pick the minimum scope (read contacts, receive forms, and so on).
Your CRM, Make or Zapier URL. We sign the body so you can verify it.
The guide publishes the field mapping into the CRM you already use.
Submit a test form and confirm the contact shows up in your CRM.
Integrations ship with the plan. Between Starter, Pro and Business the contact and send limits change, not the right to connect your CRM.
| Feature | Starter | Pro | Business |
|---|---|---|---|
| Connection | |||
| API tokens | ✓ | ✓ | ✓ |
| Signed webhooks | ✓ | ✓ | ✓ |
| Make / Zapier recipe | ✓ | ✓ | ✓ |
Numeric limits for contacts and sends are those of the plan (pricing table). We do not publish extra “integrations” quotas that are not in that table.
Every service talks to the others and lives in the same plan.
Pluxion's five core services, today paid separately — in a single plan.
7-day trial · No charge today · Free migration