Skip to main content
Use this guide to choose how leads enter Nexor, route them to the right task, and check that they arrive. Open Integrations in the sidebar to connect your account and Lead source in the agent to configure intake.
Leads you route to an active task are contacted right away per its cadence; calls wait for the task’s contact hours, and messages go right away unless the task restricts messages to its hours. Leads marked do-not-contact are not contacted, and tasks that only reply (inbound-only) don’t start outreach. This includes contacts that already exist in your system. If the task is paused, contact starts when you turn it on. Check which task receives them before you import.

​
Choose how to bring in your leads

​
Check intake before importing the rest

  1. Choose the destination task. Keep it paused while preparing the mapping if you are not ready to contact leads.
  2. Map phone, email, and the variables your task needs. Include the phone country code.
  3. Send one test contact and confirm it appears in the right task with complete information.
  4. When ready, verify the channel and working hours, set the task live, and review the first conversation with your test contact.
  5. Import a small group before connecting the full volume.
In the API, workflow_id identifies the destination task. Keep your API key on your server, never in a public form or browser. See Authentication.
If the lead does not appear, check CRM sync and lead intake. If it appears but receives no messages, check the task, channel, and working hours before sending it again.

​
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 organization intake and CRM output have separate controls, as do HubSpot input and output. 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. Personal Google Calendar and Outlook Calendar connections are completed from Meetings. Outlook does not have a separate card in the integrations grid.

​
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 October 16, 2026