In the Twilio Console, navigate to theSettings>API Keys.
SelectCreate new API Keyand choose to create either Standard or Master
API Key.
You will find your Account SID and API Credentials containingAuth Tokenin theSettings>General.
Configure Twilio integration in Google SecOps
For detailed instructions on how to configure an integration in
Google SecOps, seeConfigure
integrations.
Integration parameters
Use the following parameters to configure the integration:
Parameter Display Name
Type
Default Value
Is Mandatory
Description
Instance Name
String
N/A
No
Name of the Instance you intend to configure integration for.
Description
String
N/A
No
Description of the Instance.
Account sid
String
N/A
Yes
The ID of your Twilio Account.
Authentication token
String
N/A
Yes
Twilio token used for authentication.
SMS phone number
String
N/A
Yes
Your Twilio phone number that can be generated in the Twilio console.
Run Remotely
Checkbox
Unchecked
No
Check the field in order to run the configured integration remotely. Once checked, the option appears to select the remote user (agent).
Actions
Ping
Description
Verify that the user has a connection to Twilio via the user's device.
Parameters
N/A
Run On
This action runs on all entities.
Action Results
Script Result
If the connection is established, Script result will be True. Else: False.
JSON Result
N/A
Send SMS
Description
By using Twilio's REST API, outgoing SMS messages can be sent from specific
Twilio phone numbers to mobile phones worldwide. If multiple messages are sent
at once from a single Twilio sender (number or Alphanumeric Sender ID), Twilio
will queue them up for delivery.
Parameters
Parameter Display Name
Type
Default Value
Is Mandatory
Description
Phone Number
String
N/A
Yes
Target phone number.The phone number must include a dial code.
Message
String
Testing
Yes
Message content.
Run On
This action runs on all entities.
Action Results
Script Result
Script Result Name
Value Options
Example
is_success
True/False
is_success:False
JSON Result
N/A
Send SMS and Wait
Description
The message will be sent with a generated Google SecOps ID:<code>.
The action will wait for a response containing Google SecOps ID:<code>. This action has the role of sending SMS and waiting for a response to
a previously sent SMS message. This action also enables multiple send/wait for
reply actions within a single trigger allowing constructing automated SMS text
conversations and performing different actions based on the reply results.
Parameters
Parameter Display Name
Type
Default Value
Is Mandatory
Description
Phone Number
String
N/A
Yes
Target phone number. The phone number must include a dial code.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThis document details how to configure the Twilio integration with Google Security Operations SOAR, including obtaining necessary API credentials from your Twilio account.\u003c/p\u003e\n"],["\u003cp\u003eThe integration requires parameters such as "Account sid," "Authentication token," and "SMS phone number" to be configured, and offers the option to run remotely.\u003c/p\u003e\n"],["\u003cp\u003eThe integration provides three main actions: "Ping" to verify connection, "Send SMS" to send text messages, and "Send SMS and Wait" for sending messages and waiting for a reply.\u003c/p\u003e\n"],["\u003cp\u003eThe "Send SMS" and "Send SMS and Wait" actions require a target phone number and message content, with the latter action enabling automated SMS text conversations based on replies.\u003c/p\u003e\n"],["\u003cp\u003eThe configuration allows for the use of multiple instances, to be used in Playbooks and can be changed at any later time, if needed.\u003c/p\u003e\n"]]],[],null,["# Twilio\n======\n\nIntegration version: 13.0\n\nConfigure Twilio to work with Google Security Operations\n--------------------------------------------------------\n\n1. Log into your [Twilio account](https://www.twilio.com/login).\n\n2. In the Twilio Console, navigate to the **Settings** \\\u003e **API Keys.**\n\n3. Select **Create new API Key** and choose to create either Standard or Master\n API Key.\n\n4. You will find your Account SID and API Credentials containing *Auth Token*\n in the **Settings** \\\u003e **General**.\n\n| **Note:** For more information about API Credentials, see [API Key](https://www.twilio.com/docs/glossary/what-is-an-api-key).\n\nConfigure Twilio integration in Google SecOps\n---------------------------------------------\n\nFor detailed instructions on how to configure an integration in\nGoogle SecOps, see [Configure\nintegrations](/chronicle/docs/soar/respond/integrations-setup/configure-integrations).\n\n### Integration parameters\n\nUse the following parameters to configure the integration:\n\n| **Note:** You can make changes at a later stage if needed. Once configured, the Instances can be used in Playbooks. For detailed information on configuring and supporting multiple instances, please refer [here](https://www.manula.com/manuals/siemplify/how-to/5.5.0/en/topic/supporting-multiple-instances).\n\nActions\n-------\n\n### Ping\n\n#### Description\n\nVerify that the user has a connection to Twilio via the user's device.\n\n#### Parameters\n\nN/A\n\n#### Run On\n\nThis action runs on all entities.\n\n#### Action Results\n\n##### Script Result\n\nIf the connection is established, Script result will be True. Else: False.\n\n##### JSON Result\n\n N/A\n\n### Send SMS\n\n#### Description\n\nBy using Twilio's REST API, outgoing SMS messages can be sent from specific\nTwilio phone numbers to mobile phones worldwide. If multiple messages are sent\nat once from a single Twilio sender (number or Alphanumeric Sender ID), Twilio\nwill queue them up for delivery.\n\n#### Parameters\n\n#### Run On\n\nThis action runs on all entities.\n\n#### Action Results\n\n##### Script Result\n\n##### JSON Result\n\n N/A\n\n### Send SMS and Wait\n\n#### Description\n\nThe message will be sent with a generated Google SecOps ID: `\u003ccode\u003e`.\nThe action will wait for a response containing Google SecOps ID:\n`\u003ccode\u003e`. This action has the role of sending SMS and waiting for a response to\na previously sent SMS message. This action also enables multiple send/wait for\nreply actions within a single trigger allowing constructing automated SMS text\nconversations and performing different actions based on the reply results.\n\n#### Parameters\n\n#### Run On\n\nThis action runs on all entities.\n\n#### Action Results\n\n##### Script Result\n\n##### JSON Result\n\n N/A\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
