Query SQL
1 -
Query SQL
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 Query SQL 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 Incoming Fields
Configuration Options
Approve Contexts & Finish
Provide a list of Marketo Lead fields to which Flowsteps.io may write data. Flowsteps.io will be able to write to all active fields when Query SQL is used.
Add
Remove
| Active | Type | Marketo Field |
|---|
The Query SQL flow step uses user driven mapping for inbound fields. This means there are no preset inbound fields but you can set select which person fields the flowstep is allowed to write to.
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 Query SQL.
Global user inputs that are passed along with every call to the Query SQL 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 Query SQL 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 Query SQL flow step, and approve.
Outbound Fields
The Query SQL flow step does not use outbound fields.
Inbound Fields
The Query SQL flow step uses user driven mapping for inbound fields. This means there are no preset inbound fields but you can set select which person fields the flow step is allowed to write to.
Global Configuration Fields
Global user inputs that are passed along with every call to the Query SQL flow step service. Global attributes can be set during installation or updated from the Service Provider admin menu.
| Name | API Name | Type | Description |
|---|---|---|---|
| SQL Host | host | string | ip address or url for database connection |
| SQL User | user | string | User to connect to your database. Permissions should be read only and tables should be highly restricted |
| SQL Password | password | string | SQL database password |
| SQL database | database | string | SQL database name |
| SQL port (default 3306) | port | integer | SQL database port (default 3306) |
Flow Step Fields
These fields are set for each individual instance of the Query SQL flow step and are sent per-lead when it is called.
| Name | API Name | Type | Description |
|---|---|---|---|
| Query | query | string | Query string. Database query should only return one row. |
| Return JSON | returnField | string | When selected the entire query result will be saved to this field in JSON format |
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 Query SQL flow step is installed it becomes available in smart campaigns.
1 -
Query SQL
Add Choice
Trigger & Filter
Once the Query SQL flow step is in use the activity can be used as a trigger or a filter inside smart lists and smart campaigns.
SQL query is sent
1 - SQL query was sent