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. Open Dashboard → Admin → Integrations.
  2. Click New Integration and choose Sendblue.
  3. Enter the API Key ID and API Secret Key.
  4. Save the provider and open its webhook section.
  5. Select the Sendblue line Drip Drop should use when the provider form asks for a messaging resource.

After the credentials validate, Drip Drop can query Sendblue for available lines. Keep the API credentials private and do not place them in workflow content.

Sendblue uses a receive webhook for inbound messages. Drip Drop can auto-configure a signed receive webhook from the provider form.

  1. Open the webhook section for the saved Sendblue provider.
  2. Enable webhook setup and choose the configuration action shown by Drip Drop.
  3. If you configure the webhook manually, add the Drip Drop endpoint as a Sendblue receive webhook in Sendblue Dashboard.
  4. Return to Drip Drop and verify the inbound capability shows as configured.

Drip Drop appends its receive webhook instead of replacing the account’s existing receive webhooks. Its webhook is signed, and Drip Drop stores the Webhook Secret used to validate the sb-signing-secret header.

  • Outbound text messages are sent through the selected Sendblue line.
  • Drip Drop requests delivery status updates with each message sent.
  • Inbound messages arrive through the receive webhook rather than a mailbox connection.
  • A webhook event without the required sender or recipient phone numbers is acknowledged and skipped.
  • When signed webhooks are enabled, Drip Drop compares the incoming sb-signing-secret header with the saved Webhook Secret.
  • A missing or mismatched secret causes webhook validation to fail.
  • Drip Drop does not rotate or overwrite Sendblue’s account-wide globalSecret during setup.
Credentials and resource problems
  • Credentials rejected: verify the API Key ID and API Secret Key in Sendblue Dashboard and save them again.
  • No line appears: confirm the Sendblue account has an available line and that the credentials can list it.
Webhook problems
  • Inbound messages do not arrive: verify the receive webhook is enabled and the provider shows inbound as configured.
  • Webhook rejected: check that the saved Webhook Secret matches the sb-signing-secret value sent by Sendblue.
Inbound and sending problems
  • Delivery status is missing: confirm the provider is sending status callbacks and review the message event in Drip Drop.