Requesting New DialNexa Integrations

Request new DialNexa integrations with clear provider, action, trigger, required fields, expected result, and guidance on when custom functions or webhooks are a better fit.

Requesting new DialNexa integrations is useful when an agent or workflow needs a provider action that is not available in the catalog. A good request describes the action, trigger point, required fields, and expected result, not only the tool name.

A good integration request says what the action should do, not only the logo you want to see on a card.

Current Starting Point

Before requesting something new, check whether the current catalog already solves the job.

Need	Existing option
WhatsApp message or template follow-up	Wati.
Email follow-up or internal notification	Resend.
Owned internal API call during a call	Custom Function.
Call event delivery to another system	External Webhook.
Offline analysis or manual upload	Export call data.

What To Include In A Request

Information	Example
Tool name	The provider or product you want connected.
Action needed	Create ticket, send message, update lead, fetch appointment, or similar.
Trigger point	During a call, after a call, in a workflow, or from a campaign result.
Required fields	Lead phone, email, name, call outcome, appointment time, account id, or custom values.
Expected result	What the integration should return, create, update, or send.
Failure handling	What should happen if the provider rejects the action.

Integration Request Versus Other Options

Situation	Better option
Your team owns the destination API and needs one narrow action.	Custom Function.
Another system only needs call events or status updates.	External Webhook.
You need a full product connection usable by many workflows or agents.	Request integration.
You only need a one-time list for manual operations.	Export call data.

Submit A Useful Request

1. Search available integrations

   Avoid requesting something already in the catalog.

2. Select the target tool

   Choose the closest matching provider or tool in the request modal.

3. Describe usage context

   Explain which agent, workflow, campaign, or reporting process needs the action.

4. List field requirements

   Name the values the action needs and where those values will come from.

5. Describe success and failure

   State what should happen when the provider accepts or rejects the action.

Related Reading

Dashboard Integrations

Review the current catalog.

Custom Functions

Use API calls for narrow actions.

External Webhooks

Receive call events.

Exporting Call Data

Use offline data when automation is not required.