Does Labeeq work with Zapier or n8n?

Yes. Until a native app or node is configured, use Webhooks by Zapier or n8n's Webhook node for subscribed events and their HTTP tools for supported Labeeq API actions. Setup requires a Labeeq token, endpoint mapping and secure secret handling.

Do I need to connect a separate CRM?

No. Contacts, companies, deals, pipelines and the activity timeline are part of Labeeq, next to the conversations they came from. If you keep records in another system, move them with the public API, a webhook or a Sheets step rather than a mirroring sync.

What can the public API access?

The current REST API covers selected reads and writes for contacts, labels and lifecycle, conversations and notes, messages, leads and tasks. Personal tokens have explicit abilities and remain limited by the issuing user's role; some panel and automation functions are intentionally not exposed.

How are webhooks delivered?

Choose supported message, conversation, contact or lead events for a public HTTPS endpoint. Labeeq signs the raw JSON with HMAC-SHA256, waits up to 10 seconds and retries failed deliveries after 1, 5 and 30 minutes; order is not guaranteed.

Are API documentation and limits available?

Yes. The public developer area serves an OpenAPI 3.1 document and generated Postman collection. API calls have plan-based per-10-second and calendar-month limits, so review the response headers and current pricing matrix before sizing a workload.

Channels & integrations

Best fit

Teams with a named integration owner and a specific hand-off to a CRM, spreadsheet, automation platform or internal system—not a promise that every external record will mirror automatically.

Set up deliberately

Map stable identifiers and fields, decide which system owns each value, and test duplicates, missing email or phone values and permission changes before enabling writes.
Store tokens and one-time webhook signing secrets securely; use the narrowest practical token abilities and keep destructive contact access separate.
Test provider downtime, non-2xx responses, retries, duplicate or out-of-order events, idempotency and monthly usage alerts before relying on the connection operationally.

Confirm before launch

The CRM connection is not a general two-way database or deal sync. It looks up selected contact fields, can write allowed fields when enabled, and can pull newly created CRM contacts after auto-create is switched on.
Zapier and n8n use their generic webhook and HTTP tools until a native Labeeq app or community node is configured; available actions remain limited to the published API and webhook surface.
Plans currently allow 2, 5 or uncapped connected integrations and 10,000, 200,000 or 20,000,000 API calls per calendar month for Plus, Pro and Max, with burst limits of 30, 60 or 100 calls per 10 seconds.
External vendors control their own availability, permissions, API quotas, approval rules and charges. Labeeq cannot guarantee a third-party delivery or downstream action.