Skip to main content

Adobe Marketo Engage Self Service Flow Step triggers

Preview release

Marketo Self Service Flow connector is current in preview and subject to change.

Contact us if you have any feedback.

For the Marketo Self Service Flow connector you first need to setup an integration provider, then configure a card to use the connector. This is similar to other types of connectors.

The difference to other connectors is that you will be able to be provided a list of configured Cards/Action Flows in the Marketo Flow Step Builder.

A Marketo Self Service Flow connector is specific to an Atomic Workbench environment.

Workbench Setup

This section outlines what is needed in the Atomic platform to use a Marketo Self Service Flow connector.

Adding new Marketo integration provider

At least one Marketo integration provider needs to be created before you can configure a card to use the connector

  1. Login to your Workbench environment
  2. Navigate to Configuration > Integrations > Marketo
Marketo integration configuration in the Workbench
Marketo integration configuration in the Workbench
  1. Click Add integration
Screenshot of an input element to set the name of a new Marketo integration configuration
Click 'Add integration'
  1. Give the integration a name, and click Save
  2. Once presented with the Connector credentials, note the Client ID as this will become the API authentication token. You can come back and view the details of the integration to get the Client ID again. NOTE: For now you can discard the Secret. An issue with Marketo means we have to use API Token authentication over OAuth. You may be required to create new integration in the future to switch to OAuth authentication
Screenshot of the confirmation details including the secret which can be ignored for now
For now you can discard the secret shown above.
  1. After closing the modal, from the integration list view, also record the Service URL. This will be the URL you need to create a new Marketo Service Provider.
Screenshot of the Marketo integration config page with the newly added configuration
Copy the Service URL

Connecting with an Action Flow

This section must be completed once for each Action Flow you wish to trigger from Marketo. In the Workbench, open the Action Flow you wish to send from Marketo.

  1. At the top of the Action Flow editor graph, choose to add a new trigger.
  2. Choose Adobe Marketo Engage.
  3. Optionally give it a name.
  4. Set the trigger mode. By default this is "test" and so the Action Flow will not trigger for live users. When you are ready to go live with the Action Flow, change this to "live".

Marketo Setup

This section outlines what is needed in the Marketo platform to trigger the Atomic platform

Marketo Service Provider

A Marketo Service Provider defines the link from Marketo to the Atomic Platform. It is what allows you to view a list of configured Cards to use in Marketo

  1. Navigate to Admin > Integration > Service Providers.
Screenshot of the Service Providers are of the Marketo admin area
Service providers area of the Marketo admin area
  1. Click Add New Service.

  2. Enter Service Provider URL. This can be copied from the relevant Marketo Integration configured in the Workbench configuration, as outlined in the Workbench section above.

    Screenshot of the Flow Step setup process
    Add a new Flow Step service
  3. Click Next.

  4. When prompted, use the Client ID from the relevant Marketo Integration configured in the Workbench configuration, as outlined in the Workbench section above.

    Screenshot of the Flow Step setup process where an API key is requested
    Paste in the Client Id from the earlier configuration
  5. If a Service Provider with the same name already exists, you will be prompted to rename this Service Provider. Rename as appropriate.

    Screenshot of the Flow Step setup process where naming collisions may need to be resolved
    Resolve any naming collisions, if prompted
  6. Add Outgoing Field Mappings you want passed on each invocation of the Marketo Flow Step.

    • One of atomicId or customerId (required) - atomicId or customerId is a required mapping as this will link to an existing end user in the Atomic Platform.
    Screenshot of the Flow Step setup process where standard outgoing fields can be specified
    Add fields to include in every outgoing request to Atomic
  7. Click next, then Save to finish the setup.

Marketo Flow Step

For a campaign in Marketo you can configure to use the Service Provider Flow Step

  1. Open (or create) a campaign.
    Screenshot of the Flow tab of an campaign in Marketo
    Create or open a canpaign in Marketo
  2. From the right-hand menu, scroll to Installed Flow Steps
    Screenshot of the Flow tab of an campaign in Marketo focussed on the right-side step options column
    Scroll in the right-side panel to locate your flow step
  3. Select the Flow Step that relates to the environment added in the previous section
    • The Flow Steps should appear with the Atomic logo and named with the linked Atomic Workbench environment, Trigger Action Flow (YOUR_ENVIRONMENT)
  4. From the Action flow dropdown list select the Card you want to send.
  5. In the additional variables input, you can provide JSON payload for extra mapped attribute that are not already passed through globally with the Service Provider configuration.
    • For example, you can pass dynamic lead values or static text {"lastName": "{{lead.lastName}}", "message": "static text"}
    Screenshot of the Flow tab showing a Start Action Flow trigger step being configured
    On a case-by-case basis you can send additional data variables to Atomic
    • See note below about default variables.

The Marketo Flow is now ready to execute.

Default Action Flow variables

Some default variables are provided to the Action Flow which can be accessed in Action Flow steps.

VariableDescription
marketoLeadIdThe identifier of the marketo user. This can be used to send requests to Marketo to update a user after they action a card.
marketoAtomicIdThe atomicId property in Marketo. This is the same as the Atomic user Id.