Messaging, documents, and calendar work

Send and track an SMS

Send one idempotent Twilio SMS and return provider acceptance status.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

One message per messageId; provider delivery is not inferred from acceptance.

What to customize

Set Twilio account SID/from number and bind TWILIO_AUTH_TOKEN as a secret.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "{\"messageId\":\"m1\",\"to\":\"+12025550101\",\"body\":\"Hello\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "planned",
    "output2": "dry_run",
    "output3": "provider write suppressed"
  }
}

Returned fields

output1: accepted, planned, duplicate, or error
output2: provider status
output3: JSON SID or reason

What changes when it runs

In live mode POSTs Twilio Messages and stores the SID; other modes suppress provider writes.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe