Twilio

Use Twilio when you want Drip Drop to send SMS messages, receive inbound SMS, and optionally place phone calls through a Twilio phone number.

Note
Twilio is a phone and messaging provider. It is not an email or mailbox integration.
  • You want Drip Drop to send text messages from a Twilio phone number.
  • You want inbound SMS and message status updates to reach Drip Drop through a Twilio webhook.
  • You may also want to place calls through Twilio, depending on how your account uses phone features.
  • Confirm you have Twilio account access and permission to manage the phone number you want to use.
  • Make sure at least one Twilio phone number is available on the account.
  • Have the Account SID and Auth Token ready.
  • Use a safe test number for the first send and inbound test.
  1. Open Dashboard → Admin → Integrations.
  2. Click New Integration and choose Twilio.
  3. Enter the Account SID and Auth Token.
  4. Save the provider, then open the Webhook section.
  5. Select the Twilio phone number Drip Drop should use.

After the credentials are saved, Drip Drop can list the phone numbers on the Twilio account and help configure the webhook for the selected number.

Twilio uses one webhook URL per phone number resource. Drip Drop uses that webhook for inbound SMS and delivery or status callbacks.

  • If the selected number already points to a different webhook URL, Drip Drop can show a conflict instead of silently replacing it.
  • If auto-configure is available, Drip Drop can set the SMS URL and status callback for the selected phone number.
  • If auto-configure is not available, add the Drip Drop URL manually in Twilio Console.
  • Outbound SMS is sent through the selected Twilio number and Drip Drop stores the Twilio message SID after success.
  • Inbound messages are webhook-driven, not mailbox-based.
  • The same webhook path is used for incoming SMS and status callbacks, so both need to be configured correctly.
  • Twilio can also place calls; keep expectations high-level unless your team has separate voice setup docs.

Twilio provider settings can expose Drip Drop internal tracking toggles where available. Keep those separate from email-style tracking language.

  • If Signed Webhook Validation is enabled, Drip Drop validates the incoming Twilio signature using the account auth token.
  • If Signed Validation is off, Drip Drop can accept the request without that extra signature check.
  1. Open the correct phone number in Twilio Console.
  2. Set the SMS or messaging webhook URL to the Drip Drop webhook URL.
  3. Set the status callback URL to the same Drip Drop endpoint if your current product flow expects delivery updates there.
  4. Save the changes and return to Drip Drop to verify the configured state.
Credentials and resource problems
  • If the provider cannot connect, confirm the Account SID and Auth Token are correct.
  • If no phone numbers appear, make sure the Twilio account actually owns a compatible number.
  • If the wrong number was selected, choose the exact number that should send and receive messages for Drip Drop.
Webhook problems
  • If Drip Drop reports a conflict, check whether the number already points to another webhook URL in Twilio.
  • If inbound messages or status updates do not appear, verify the webhook URL and callback settings on the Twilio number.
  • If signed validation fails, check whether the saved auth token still matches the Twilio account sending the webhook.
Inbound and sending problems
  • If messages send but replies do not appear, test the inbound webhook path with a real SMS to the configured Twilio number.
  • If status updates are missing, verify the status callback is pointed at Drip Drop as expected.
  • See Integrations for the shared provider setup flow and provider management basics.
  • Compare Telnyx if you want a similar phone and SMS workflow with messaging profiles instead of Twilio phone-number configuration.