Twilio SMS inside Notifly workflows, on your own account.

These are the fields the dashboard asks for when you connect Twilio, quoted from the create form.

• Data residency region. EU (Ireland) sends through Twilio's ie1 region via the dublin edge; US (default) uses Twilio's default endpoint.
• From. The sender of every SMS from this integration. A trigger can set another one with overrides.providers.twilio.from.

1. Sign in at app.notifly.io, open Integration Store in the sidebar and choose Connect Provider.
2. In the Connect Integration sheet, open the SMS tab (or search across channels), find Twilio and choose Connect.
3. Pick the environment the integration belongs to. Development and Production keep separate integrations, so you can point each at a different Twilio account or key.
4. Fill in Delivery Provider Credentials with the fields in the table above, then choose Create Integration.
5. A new integration starts switched on as both Active Integration and Primary Integration, so SMS steps in that environment send through Twilio by default. If the environment already has a primary SMS integration, the dashboard asks before replacing it.

Your backend triggers a workflow; Notifly renders the SMS step and sends it with Twilio. The phone number in to is saved on the subscriber, so later triggers only need the subscriberId.

// npm install @notiflyio/api@0.1.26
import { Notifly } from "@notiflyio/api";

const notifly = new Notifly({ security: { secretKey: process.env.NOTIFLY_SECRET_KEY } });

await notifly.trigger({
  workflowId: "login-code",
  to: { subscriberId: "user_123", phone: "+15551234567" },
  payload: { code: "482913" },
  overrides: {
    // Merged into the options of Twilio's messages.create for this send.
    providers: { twilio: { validityPeriod: 300 } },
  },
});

Prefer plain HTTP? The same trigger is POST https://api.notifly.io/v1/events/trigger with an Authorization: ApiKey header and a body of { "name", "to", "payload" }.

An SMS leaves two records, held by two different parties. Which one you must keep in the EU decides whether this setup is enough.

• At Twilio. Choose EU (Ireland) and Notifly sends through Twilio's ie1 region. For SMS sent through the Programmable Messaging API in IE1, Twilio states that messages are processed and stored exclusively in IE1 up to the point they reach its connections with telecom providers. Twilio lists exceptions: its subprocessors, carrier routing that can span regions, and support access from outside the EU. Create the Twilio credentials for that region, and check Twilio's Regions documentation for what your products support.
• At Notifly. Notifly keeps its own records of each send: the recipient phone number, your trigger payload and Twilio's response, shown in the activity feed. They expire after a fixed retention period. Notifly runs as one hosted deployment with no region choice today, so those records are not EU-only. If strict EU storage of message data is a requirement, contact us before you rely on Notifly for it.

• One messages.create call per SMS. With the rendered body, the subscriber's phone as to and your From number.
• Your Twilio options. Anything under overrides.providers.twilio is merged into that call, such as statusCallback or validityPeriod.
• A SID you can join on. The Message SID Twilio returns is stored on the Notifly message.
• No phone, no call. A subscriber without a phone number is skipped and recorded, not sent to Twilio.