Sendblue

Use Sendblue when you want Drip Drop to send text messages, receive inbound messages, and process delivery status callbacks through your Sendblue account. Sendblue is a messaging provider, not an email or mailbox integration.

Note
The current Drip Drop connector exposes Text Message capability. Sendblue’s broader product may support other channels, but this guide covers the behavior implemented in Drip Drop.
  • You want Drip Drop to send text messages through a Sendblue line.
  • You want inbound messages to reach Drip Drop through a Sendblue receive webhook.
  • You want delivery status callbacks recorded for messages sent by Drip Drop.
  • Confirm you have Sendblue account access and permission to manage its API credentials.
  • Have the API Key ID and API Secret Key ready. Sendblue provides these in the account dashboard.
  • Make sure the account has a usable sending line and choose a safe test number.
  1. From the dashboard, open Integrations → Text Message, then select New Integration.
  2. Choose Sendblue.
  1. Enter a clear Name, then enter the API Key ID and API Secret Key from Sendblue.
  2. Select Save & Continue. Drip Drop creates the integration, moves to Webhooks, and starts importing available Sendblue lines.
Enter a name, API Key ID, and API Secret Key, then select Save & Continue.

Select Configure Webhook to add Drip Drop as a signed Sendblue receive webhook, then select Verify Webhook. Select Save Webhook to continue, or Skip for now to configure it later.

Configure and verify the Sendblue receive webhook, then save the webhook settings or skip this step for now.

Add or sync at least one Sendblue line. Flows cannot send until a sender exists. Select Continue, or select Skip for now and add a sender later from the integration settings.

Add or sync a Sendblue line for flows to send from, then select Continue.

Review stored credentials, webhook readiness, and senders. Credentials stored confirms only that values are saved; Check credentials, Verify webhook, and Sync from provider perform live Sendblue checks. Resolve any warnings now, or select Done and return later from the integration settings.

Review stored credentials, webhook readiness, and senders before selecting Done.

Configure and Verify the Receive Webhook

Sendblue uses a receive webhook for inbound messages. Configure Webhook adds a signed Drip Drop receive webhook and saves its Webhook Secret.

  1. On Webhooks, select Configure Webhook.
  2. Select Verify Webhook and confirm Webhook is correctly configured.
  3. For manual setup, add the displayed Drip Drop endpoint as a Sendblue receive webhook and save the same Webhook Secret in Drip Drop.
  4. Select Save Webhook to continue.

Drip Drop adds its signed receive webhook without replacing the account’s existing receive webhooks. It stores the Webhook Secret used to validate incoming events.

Signed Webhook Validation

  • Configure Webhook enables signed validation and saves the Webhook Secret automatically.
  • Incoming events are rejected when their signing secret is missing or does not match the saved Webhook Secret.
  • If the Sendblue account already has an account signing secret, Drip Drop uses it without changing the account-wide value.

Outbound SMS and Media

  • Outbound SMS is sent from a configured Sendblue sender. A message can include one media attachment.

Delivery-Status Events

  • Drip Drop requests status updates with each send and records delivered, opened, or bounced events for the Sendblue statuses it recognizes.

Inbound Messages

  • Inbound messages arrive through the receive webhook. Drip Drop records the text and keeps a provider media URL in the message metadata when Sendblue supplies one.
  • A webhook event without the required sender or recipient phone numbers is acknowledged and skipped.
Credentials and Resource Problems
  • Credentials rejected: confirm the API Key ID and API Secret Key in Sendblue Dashboard, re-enter them in Connect, then select Check credentials in Verify.
  • No sender appears: confirm the Sendblue account has an available line, then select Sync from provider in Senders.
Webhook Problems
  • Inbound messages do not arrive: select Verify webhook in Verify. If no matching URL is registered, return to Webhooks and select Configure Webhook.
  • Webhook rejected: confirm the saved Webhook Secret matches the secret configured for the Sendblue receive webhook.
Inbound and Sending Problems
  • Delivery status is missing: select Verify webhook in Verify, then review the message event in Drip Drop.
  • See Text Message for channel setup and provider selection.
  • Compare Twilio for a phone-number-based SMS and MMS workflow.
  • Compare Telnyx SMS & MMS for a messaging-profile-based SMS and MMS workflow.