Twilio Messaging

The Twilio Messaging Node enables you to send and receive SMS messages, manage Messaging Services, and interact with Twilio's comprehensive messaging platform through its REST API.

Revision History

1.0.0.0 Initial release

Properties

Connection

Type: Connection Input
The Connection Property contains your Twilio authentication credentials and optional regional settings.

AccountSid
Type: String Input
Your Twilio Account SID, which is found in your Twilio Console dashboard. This uniquely identifies your Twilio account.

ApiKey
Type: Secret Input
Your Twilio API Key SID. You can create API keys in your Twilio Console under Account Info → Go to API Keys.

ApiKeySecret
Type: Secret Input
The secret associated with your Twilio API Key. Keep this secure and never share it publicly.

Region
Type: String Input
Optional. Specify a Twilio region (e.g. us1) to optimise latency for your geographic location.

Edge
Type: String Input
Optional. Specify a Twilio edge location to further optimise network routing.

OperationId

Type: String Input
A unique identifier for the specific Twilio API operation you want to perform. This is automatically populated when you select a sample from the Node's Sample list.

Description

Type: String Input
A human-readable description of the current operation. This helps understand what the Node is currently set up to do.

Type: JSON Input
The JSON payload containing the parameters for your Twilio API Request. The required structure depends on the OperationId selected. An example body will be automatically populated for you.

Response

Type: JSON Output
The JSON response returned by the Twilio API after executing your Request.

Setting up your Twilio Connection

Before you can use the Twilio Messaging Node, you must first create a Twilio Connection in Flowgear with your Twilio Account details. Depending on your needs and how you would like to use the Node, you have the following two options for account organisation. Please note that both paths use the same secure API Key authentication method recommended by Twilio.

Option 1: Use a Flowgear-Managed Subaccount

Flowgear can create and maintain a subaccount for you under our main Twilio account. Subaccounts keep usage, numbers, and billing neatly separated, while still sharing the parent account's balance and governance controls. To proceed with this option, please contact our support team with this request, and we will assist you with the next steps.

Option 2: Use your own Twilio Account

Log into your Twilio Console.
On your desired Account's Dashboard, find your AccountSid. For security, the Node authenticates with an API key SID and secret rather than your master Auth Token.
Navigate to the Account Info section at the bottom of the page, and click on the Go to API Keys link.
Create a new API Key, or use an existing one. We recommend a key of type Standard for the best security. Copy the generated ApiKey SID and ApiKeySecret.
In Flowgear, create a new Twilio Messaging Connection.
Paste in your AccountSid, ApiKey, and ApiKeySecret into the corresponding fields on the Connection.
Click Save, then click Test.
Flowgear will now attempt a test API call to a generic Twilio endpoint to ensure your credentials are valid.

If the test is successful (✓), your credentials are valid.

If it fails (✗), the test will return an error message, and you may need to double-check that your Connection details are correct. If this problem persists, contact support for assistance.

Phone Numbers

In order to use this Node, you need to have a Twilio-verified number that you can use to send messages from. Again, there are various options, depending on your preferences and how you would like to use the Node. You can port your phone numbers into Twilio, but note that this requires a lengthy setup time and paperwork for this process to be accepted. Alternatively, you can buy an official Twilio number for your desired location.

There is also quite a lot of regulatory information that may guide your decision-making, which for South Africa, is linked in the below "See Also" section.

Feel free to contact support for any assistance in this matter for your specific use case.

Using the Node

After configuring your Connection, you can start making Twilio Messaging API calls. The easiest way to get started is by using the pre-built Node Samples available via the Node.

Sending a Message

SMS

To send a standard SMS, provide the recipient (To), the sender (From), and the message content (Body).

{
    "To": "+1234567890",
    "From": "+0987654321",
    "Body": "Hello from Flowgear!"
}

MMS

To send a message with media, add the MediaUrl property.

Note: To test MMS, you need a Twilio phone number that is MMS-enabled. Standard trial numbers may not support this feature.

{
    "To": "+1234567890",
    "From": "+0987654321",
    "Body": "Check out this image!",
    "MediaUrl": [
        "https://example.com/image.jpg"
    ]
}

WhatsApp Message

To send a message via WhatsApp, prefix the To and From numbers with "whatsapp:".

Note: Using the WhatsApp Business Platform requires an upgraded Twilio account and completion of the Meta Verification process.

{
    "To": "whatsapp:+1234567890",
    "From": "whatsapp:+0987654321",
    "Body": "Hello from Flowgear, on WhatsApp!"
}

Scheduled Message

You can schedule a message to be sent in the future by providing a SendAt time in ISO-8601 format and setting ScheduleType to "fixed". This message needs to be sent using a Messaging Service (see below).

Note: The SendAt time must be in UTC and at least 5 minutes in the future.

{
    "To": "+1234567890",
    "MessagingServiceSid": "MG1234567890abcdef1234567890abcdef",
    "Body": "Reminder: Your appointment is tomorrow",
    "ScheduleType": "fixed",
    "SendAt": "2025-07-05T14:30:00Z"
}

Receiving a Message

This typically involves setting up Twilio webhooks to receive incoming messages. See the Twilio documentation for webhook configuration details.

Advanced Features

Messaging Services

For enhanced features like number pooling, scheduling, and automatic failover, you can send messages using a Messaging Service instead of a From number. First, create a Messaging Service, add a sender phone number to it, and then, use the MessagingServiceSid in your Request.

{
    "To": "+1234567890",
    "MessagingServiceSid": "MG1234567890abcdef1234567890abcdef",
    "Body": "Message sent via Messaging Service"
}

Message Feedback

Track message delivery and user engagement. Create a Message Feedback, linked to the SID of a Message created. When a response or user action is received in response to this Message, update the attached Message Feedback with the "Outcome". Use this subresource to record user engagement (e.g. confirmed, delivered) and improve deliverability analytics.

{
    "Outcome": "confirmed"
}

Pricing Lookups

Get pricing information for different countries.

Remarks

Please note that a few features are still undergoing final testing. If you encounter any unexpected behaviour when sending MMS or WhatsApp messages, or when working with Short Codes, please reach out to our support team so we can investigate and resolve the issue promptly.
The Node automatically converts the Request JSON into the application/x-www-form-urlencoded format required by the Twilio API.
All date and time values, such as SendAt for scheduled messages, must be provided in ISO 8601 format, e.g. 2025-07-04T14:30:00Z.