> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting DialNexa Integrations

> Connect DialNexa integrations such as Wati and Resend with credentials, hosted flows, API keys, sender email, validation, disconnect, and connection status review.

Connecting DialNexa integrations creates an organization-level connection that workflows and eligible agent actions can use. Wati and Resend use credential-style setup in the dashboard, and other future providers may use hosted connection flows.

<Warning>
  A connection saved without validation is like a locked door with a handwritten key taped nearby. Check it before building on it.
</Warning>

## Connection Methods

| Method      | How it works                                                      | Examples                                            |
| ----------- | ----------------------------------------------------------------- | --------------------------------------------------- |
| Credentials | User enters required fields in DialNexa.                          | Wati API key, Resend API key, Resend from email.    |
| Hosted flow | DialNexa opens a provider-managed connection URL where supported. | Future or requested providers may use this pattern. |
| Validation  | DialNexa checks whether the stored connection can be used.        | Use before workflow launch or agent exposure.       |
| Disconnect  | Removes the organization connection for the provider and adapter. | Use when rotating credentials or removing access.   |

## Provider Credential Requirements

| Provider | Required connection fields | Action depends on                                                               |
| -------- | -------------------------- | ------------------------------------------------------------------------------- |
| Wati     | API key.                   | Valid WhatsApp templates, phone numbers, message body, and template parameters. |
| Resend   | API key and from email.    | Verified sender setup, recipient email, subject, and text body.                 |

## Connection Statuses

| Status       | Meaning                                                              | What to do                                          |
| ------------ | -------------------------------------------------------------------- | --------------------------------------------------- |
| Connected    | Credentials are stored and validation succeeded.                     | Safe to use in workflows, then monitor invocations. |
| Pending      | Connection exists but has not completed validation or hosted return. | Validate again or complete the provider flow.       |
| Error        | The provider or adapter returned a failure.                          | Open the error, update credentials, then validate.  |
| Disconnected | No active organization connection is available.                      | Reconnect before using actions.                     |

## Connect And Validate

<Steps>
  <Step title="Open Integrations">
    Choose the provider row, such as Wati or Resend.
  </Step>

  <Step title="Enter required credentials">
    Add API key and any provider-specific fields. For Resend, include the from email that should send messages.
  </Step>

  <Step title="Save the connection">
    Save credentials before wiring workflows or agent actions.
  </Step>

  <Step title="Validate">
    Confirm the provider accepts the connection. Validation failure is cheaper here than inside a live campaign.
  </Step>

  <Step title="Use one test action">
    Run a small workflow or action test and inspect invocation evidence.
  </Step>
</Steps>

## Connection Troubleshooting

<AccordionGroup>
  <Accordion title="Configured but actions fail">
    Validate the connection and inspect invocation errors. The action may be missing required fields even when credentials are valid.
  </Accordion>

  <Accordion title="Pending status remains">
    Hosted connection may not have completed, or validation may not have run after saving credentials.
  </Accordion>

  <Accordion title="Resend sender fails">
    Confirm the from email belongs to the connected Resend setup and is allowed to send.
  </Accordion>

  <Accordion title="Wati template fails">
    Confirm the template exists, is approved, and receives the correct number of parameters.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="WhatsApp With Wati" icon="message-circle" href="/dashboard-integrations/whatsapp-with-wati">
    Connect and send WhatsApp messages.
  </Card>

  <Card title="Email With Resend" icon="mail" href="/dashboard-integrations/email-with-resend">
    Connect and send emails.
  </Card>

  <Card title="Using In Workflows" icon="workflow" href="/dashboard-integrations/using-integrations-in-workflows">
    Use connected actions.
  </Card>

  <Card title="Integration Functions" icon="settings" href="/dashboard-integrations/integration-functions">
    Debug action execution.
  </Card>
</CardGroup>