Skip to main content
Start on Settings → Integrations. The grid is organized by channel, CRM and lead source, calendar, AI model, developer surface, and other business systems.
Nexor Integrations grid grouped by product area

The Integrations grid in staging on September 7, 2026. Optional cards may vary by account.

Dedicated screen or custom connection?

A card with its own Nexor screen means the product has provider-specific setup and status. It does not mean every connector has the same direction or features. For example, Zoho is currently outbound-only, while HubSpot has separate input and output controls. Use a custom connection when your system has no dedicated card. This is the current path for Salesforce, Flowlu, and an in-house CRM. Depending on what the external system can do, connect it with an incoming webhook, the Public API, an outgoing webhook, or an agent HTTP tool.
Do not treat a logo or source label elsewhere in Nexor as proof of a ready-made connector. Salesforce and Flowlu do not have dedicated integration cards.

CRM and lead sources

Other cards in the grid

Instagram and Messenger appear only when the optional Meta messaging feature is enabled for the account. A self-hosted LLM also depends on account configuration even when its card is visible. Google Calendar may send you to the Meetings connection flow rather than a separate integration page.

If your system is not listed

  1. Confirm whether it can send HTTPS webhooks or make authenticated HTTP requests.
  2. Use an incoming lead webhook for push-based lead delivery.
  3. Use the Public API when your system can choose the receiving agent on each request or needs broader lead operations.
  4. Add outgoing webhooks or agent HTTP tools only for the events and actions your external system needs.
  5. Test with synthetic data before enabling live lead traffic.
Nexor does not promise a universal two-way sync for a custom system. The exact behavior is the set of input and output paths you configure.
Last modified on September 7, 2026