Skip to main content

Connect

Establishes a connection to the Twilio API using your account credentials. This node creates a connection ID that can be reused across multiple Twilio nodes, eliminating the need to enter credentials repeatedly.

Common Properties

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If ContinueOnError property is true, no error is caught when the project is executed even if Catch node is used.

Input

  • n/a - This node has no input parameters.

Output

  • Connection Id - A unique identifier for the Twilio connection session. Use this ID in subsequent Twilio nodes (Send SMS, Voice Call, etc.) to authenticate API requests.

Options

  • Account SID - Your Twilio Account SID for API authentication. This can be found in your Twilio Console dashboard at console.twilio.com.
  • Token - Your Twilio Auth Token for API authentication. This can be found in your Twilio Console dashboard.
tip

Store your Account SID and Auth Token in Robomotion Vault for security. Never hardcode credentials in your flows.

Example

Basic Connection Setup

This example shows how to connect to Twilio and use the connection ID in subsequent nodes:

  1. Add a Connect node to your flow
  2. Configure the Account SID and Token in the Options
  3. The node outputs a Connection Id
  4. Pass this Connection Id to other Twilio nodes (Send SMS, Voice Call, etc.)
Connect Node
└── Output: connection_id = "conn_abc123"
└── Send SMS Node (uses connection_id as input)

Reusing Connections

Once you have a Connection Id, you can use it across multiple Twilio operations in your flow:

Connect
├── Send SMS (uses connection_id)
├── Send WhatsApp Message (uses connection_id)
└── Voice Call (uses connection_id)

Tips

  • Connection Reuse - Create one connection at the start of your flow and reuse the Connection Id across multiple Twilio nodes.
  • Credential Security - Always use Vault credentials instead of hardcoding your Account SID and Auth Token.
  • Error Handling - Wrap the Connect node in a Try-Catch block to handle authentication failures gracefully.
  • Testing - Verify your credentials are correct by testing with a simple Send SMS operation.

Common Errors

Invalid Credentials

Error: "ErrInvalidArg: No SID Value" or "ErrInvalidArg: No Token Value"

Solution:

  • Ensure your Account SID and Auth Token are correctly entered
  • Verify the credentials are stored properly in the Vault
  • Check that the Vault credential name matches the configuration

Authentication Failed

Error: Authentication fails when using the connection

Solution:

  • Verify your Account SID and Auth Token are active in the Twilio Console
  • Ensure your Twilio account is in good standing and not suspended
  • Check that you're using the correct credentials (not test credentials in production)
  • Regenerate your Auth Token if it has been compromised