Integrations

Use Integrations to connect the provider accounts Drip Drop uses for email, SMS, phone-capable messaging, and AI-assisted content. This page is the setup hub; provider-specific setup pages live underneath it.

Note
Integrations are managed from the owner-only Admin area. If you do not see Admin, ask an organization owner to connect providers or confirm your access.
The Integrations table showing connected providers, methods, statuses, tags, usage, and verification columns.
  • Decide which channel you need first: Email, SMS/phone, or AI.
  • Make sure you have organization owner access in Drip Drop, because Admin is owner-only.
  • Have the provider account, OAuth access, API key, or app password ready before starting.
  • Use a safe test contact before sending production messages.
  1. Open Admin.
  2. Choose Integrations.
  3. Review the existing provider accounts and their status before adding a new one.
  1. Choose Add Provider or open an existing provider account.
  2. Select the provider type.
  3. Enter the required credentials or start the OAuth connection.
  4. Save the provider.
  5. Confirm the provider appears in the Integrations list.
The Add Provider modal with the provider picker, status field, connector-specific fields, tracking, tags, and save actions.

Choose the provider that matches the service you want Drip Drop to use. The provider picker on staging includes Gmail, Outlook, Email, Mailgun, Sendgrid, Telnyx, Twilio, ChatGPT, and Claude. OAuth providers may save as Gmail (OAuth) or Outlook (OAuth) after connection.

Click on each of the providers for provider specific documentation.

Email Providers

Gmail: Connect a Google mailbox with OAuth or an app password.
Outlook: Connect a Microsoft mailbox with OAuth or an app password.
Email: Connect a standard SMTP provider, with optional IMAP settings when incoming mail is needed.
Mailgun and Sendgrid: Connect API-based email sending providers, with webhook, tracking, and inbound parse settings where configured.

SMS and Messaging Providers

Twilio and Telnyx: Connect providers used by SMS and phone-capable flow blocks. Telnyx and Twilio can auto-configure webhooks after you choose the relevant messaging resource.
Sendblue: Use with Text Message, Notify and AI blocks to send via iMessage and SMS. Add your Sendblue API Key ID and Secret Key to auto-configure webhooks.

AI Providers

ChatGPT, OpenRouter and Claude: Connect AI providers with an API key, verify the key, and choose a default model when models are available.
A provider detail form showing provider-specific credentials, webhook, tracking, and inbound settings.

After a provider is connected, it becomes available where matching flow blocks ask for a provider. Email providers are available in email blocks, SMS providers are available in text message blocks, phone-capable providers can be used by phone-capable blocks, and AI providers are available where AI provider selection is supported.

A flow block selecting a compatible connected provider for use in a flow.

Read Provider Status

  • The Integrations table shows each provider's Service, Methods, Status, Tags, Last Used, Created Date, and Last Verified for AI providers.
  • Provider statuses are: Active, Paused, Attention Required, and Archived. The table filter currently exposes: Active, Paused, and Archived.
  • An inbound status dot can appear next to the provider name when inbound capabilities are configured, partially configured, or missing.
  • For webhook-capable providers, new provider setup can show Save & Configure Webhook. Existing provider forms can show Enable Webhooks, Configure Webhook, Verify Webhook, Track Clicks, Track Opens, signed webhook fields, and inbound parse fields depending on the provider.
Provider is missing from a flow block
  • Confirm the provider was created under Admin → Integrations.
  • Confirm the provider type matches the block type you are configuring.
  • Refresh the page after saving a new provider if the block was already open.
Credentials or OAuth connection fails
  • Check the provider account credentials, OAuth permissions, API key, app password, webhook signing key, or selected phone/messaging resource, depending on the provider type.
  • For OAuth providers, reconnect the account if authorization expired or was revoked.
  • For API-key providers, create a fresh key in the provider console if the existing key may be invalid, then save or verify the provider again.
  • For webhook providers, use Configure Webhook when auto-configuration is available, or copy the webhook URL into the provider console and then use Verify Webhook.
  • For AI providers, use Verify API Key and confirm the account has access to the selected model.
Sends fail after setup
  • Check History for send errors.
  • Confirm the provider account is active and allowed to send through the selected channel.
  • Use a test contact before enrolling real contacts.

Getting Started: Follow the first setup walkthrough.

Templates: Create message content that uses connected providers.

Flow blocks: Choose matching providers inside email, text message, phone-capable, and AI-supported blocks.