Twilio Phone Validation
1 -
Validate Phone with Twilio
Add Choice
Installing a custom flow step requires Admin permissions in Marketo. Apart from the Installation URL, all other aspects of a serviced may be edited after completing initial onboarding by drilling down into the service detail screen from the Service Providers grid.
In Marketo navigate to Admin → Service Providers and click Add New Service
From here, follow the bellow steps to install and configure the flow step.
Flow Step Service
Confirm installation
To begin installation, you’ll need to first enter the install URL of the Validate Phone with Twilio flow step shown above. This URL gives Marketo the basic information it needs to connect to and configure the flow step.
Flow Step Service
Enter Credentials
Please provide an API Key. Valid API credentials from Flowsteps.io are required to complete installation.
After you enter the installation URL you will be asked to enter your API Key. When you save your credentials, Marketo will attempt to verify that it is valid. If the credentials provided are invalid, you’ll see an error indicating this.
Flow Step Service
Map Outgoing Fields
Map Incoming Fields
Configuration Options
Flowsteps.io has provided a list of required and optional fields to map to Marketo Lead fields. Fields which are mapped and active will be sent to the service provider when Validate Phone with Twilio is invoked from a Smart Campaign. Required mappings must be completed and be active in order to complete service installation.
| Active | External Field | Type | Description | Marketo Field |
|---|---|---|---|---|
|
|
* MobilePhone | string | MobilePhone |
MobilePhone
|
|
|
Phone | string | Phone |
Phone
|
The Outgoing Fields, are sent to the Validate Phone with Twilio flow step. Be sure to activate and map all required fields.
After you enter the installation URL you will be asked to enter your API Key. When you save your credentials, Marketo will attempt to verify that it is valid. If the credentials provided are invalid, you’ll see an error indicating this.
Flow Step Service
Map Incoming Fields
Configuration Options
Approve Contexts & Finish
Flowsteps.io has provided a list of response mappings to map to Marketo Lead fields. Fields which are mapped and active may be written to by Flowsteps.io, when processing of Validate Phone with Twilio is complete. Response Mappings are not required to complete service installation, but the service may not function as expected if mappings are not provided.
| Active | External Field | Type | Description | Marketo Field |
|---|---|---|---|---|
|
|
* PhoneStatus | string | Returns Valid or Invalid |
PhoneStatus
|
|
|
PhoneCountry | string | Returns 2-digit ISO country code |
PhoneCountry
|
|
|
PhoneDetails | text | Returns Carrier and phone type |
PhoneDetails
|
|
|
MobileStatus | string | Returns Valid or Invalid |
MobileStatus
|
|
|
MobileCountry | string | Returns 2-digit ISO country code |
MobileCountry
|
|
|
MobileDetails | text | Returns Carrier and phone type |
MobileDetails
|
The Validate Phone with Twilio flow step uses set inbound fields. Below are the fields that are returned from the flow step and can be written to the person based on the mapping you set.
Flow Step Service
Map Incoming Fields
Configuration Options
Approve Contexts & Finish
Flowsteps.io has provided a list of required and optional configuration settings. These settings will be used globally by Validate Phone with Twilio.
Global user inputs that are passed along with every call to the Validate Phone with Twilio flow step service. Global attributes can be set during installation or updated from the Service Provider admin menu.
Flow Step Service
Map Incoming Fields
Configuration Options
Approve Contexts & Finish
Flowsteps.io is requesting access to the following data contexts. When Validate Phone with Twilio is invoked from a Smart Campaign, the data from these objects will be sent as contextual information to Flowsteps.io, such that processing may be completed.
Subscription
Program
Program Member
Smart Campaign
Trigger
My Tokens
Finally review the context data that will be sent to the to Validate Phone with Twilio flow step, and approve.
Outbound Fields
The Validate Phone with Twilio flow step uses set outbound fields. Below are the person fields that are sent to the flow step based on the mapping you set.
| Name | API Name | Type | Description |
|---|---|---|---|
| MobilePhone | MobilePhone | string | MobilePhone |
| Phone | Phone | string | Phone |
Inbound Fields
The Validate Phone with Twilio flow step uses set inbound fields. Below are the fields that are returned from the flow step and can be written to the person based on the mapping you set.
| Name | Suggested Marketo Field | Description |
|---|---|---|
| PhoneStatus | PhoneStatus | Returns Valid or Invalid |
| PhoneCountry | PhoneCountry | Returns 2-digit ISO country code |
| PhoneDetails | PhoneDetails | Returns Carrier and phone type |
| MobileStatus | MobileStatus | Returns Valid or Invalid |
| MobileCountry | MobileCountry | Returns 2-digit ISO country code |
| MobileDetails | MobileDetails | Returns Carrier and phone type |
Global Configuration Fields
Global user inputs that are passed along with every call to the Validate Phone with Twilio flow step service. Global attributes can be set during installation or updated from the Service Provider admin menu.
| Name | API Name | Type | Description |
|---|---|---|---|
| Twilio Phone Verification API Key | api_token | string | Twilio Phone Verification API Key |
Flow Step Fields
These fields are set for each individual instance of the Validate Phone with Twilio flow step and are sent per-lead when it is called.
| Name | API Name | Type | Description |
|---|---|---|---|
| Select fields to validate | validate | string | Select fields to validate |
Context Data
| Name | Description |
|---|---|
| Program Context | Data about the program where the flow step was triggered including name, id, type, workspace etc. |
| Campaign Context | Data about the campaign where the flow step was triggered, including name, id, type, status, etc. |
| Trigger Context | Context around the trigger that initiated the smart campaign where the flow step was called. No data is sent if the flow step was called in a batch campaign. |
| Subscription Context | General data about the subscription including munchkinId and name |
Flow Step
Once the Twilio Phone Validation flow step is installed it becomes available in smart campaigns.
1 -
Validate Phone with Twilio
Add Choice
Trigger & Filter
Once the Twilio Phone Validation flow step is in use the activity can be used as a trigger or a filter inside smart lists and smart campaigns.
Validate Phone with Twilio is sent
1 - Validate Phone with Twilio was sent