Marketo Module Reference Guide

Applies to

Bridge by Smartsheet

The Marketo integration for Bridge has a number of different modules you can set up in your workflow.

You can use data references in all fields that’ll appear in the Create Folder, Find Folder by Name, Get Folder, and Update Folder modules.

Add User to Static List

Static List ID

This field is mandatory. It is where you specify the static list in Marketo where the module should add your lead. 

To find your static list ID, navigate to your static list using your web browser. Then, in the URL, look for the first six-digit value between the letters.

Your URL should look similar to this: … marketo.com/#ST111222B2LA1. The static list ID in this example is 111222.

Email

This is a mandatory field that a module uses to identify lead IDs in the Marketo lead database.

The module will implement actions depending on the value on this field. 

Workflow for leads with the email address in this field

  1. The module will note the lead ID. 
  2. Then, it’ll use the lead ID to add the lead to the specified static list. 

Workflow for nonexistent leads

  1. The module will add the lead to the lead database using any additional information in the module about it. 
  2. Then, it’ll use the new ID to add the lead to the static list.

First Name

This is an optional field where you can set a lead's first name.

If the module adds a new lead to the database, it’ll use the value in this field in the corresponding field in Marketo.

Last Name

This is an optional field where you can set a lead's last name.

If the module adds a new lead to the lead database, it’ll use the value in this field in the corresponding field in Marketo.

Company

This is an optional field where you can set a lead's company name.

If the module adds a new lead to the lead database, it’ll use the value in this field in the corresponding field in Marketo.

Other Fields

In this module, you’ll also see a set of other optional field names and values.

If the module adds a new lead to the lead database, it’ll use the value in the corresponding field in Marketo.

Currently, you can’t use this module to update information in the lead database if the lead exists in Marketo. 

For example, the module used the email of an existing lead, but their first name changed since they were first added. The module won’t be able to update the lead with the new name.

Here’s another example:

Key

Value

title

Director of Engineering

mobilePhone

+44 75777 77777

Marketo provides a list of standard fields that exist in almost all lead databases. Use the REST API Name for your field names.

Create Folder 

When this module detects the trigger you set up, it will create a folder in Marketo.

Marketo Create Folder

Create Folder fields

Folder Name 

This is where you can assign a name for the folder you’re creating. 

Parent Folder ID 

This is the ID of the parent folder. Use the Find Folder by Name module if you don’t yet have the ID. 

Parent Folder Type

Choose one type from these options:

  • Folder  
  • Program

Customize Folder 

In this section, add a brief description of the folder. You can enter up to 2,000 characters in the Folder Description field.

Once Bridge executes the Create Folder module in a workflow, you’ll see the following data groups:

  • Data
    • accessZoneId
    • createdAt: The creation date and time
    • description: The folder description 
    • folder
      • id: The ID for the folder
      • type: Can be Folder or Program
    • folderType: Reflects the usage of the folder

      Usage

      folderType

      Contains multiple types of assets

      • Marketing Folder
      • Program

      Contains only a that type of asset, subfolder, and template version of that UI type

      • Email
      • Email Template
      • Landing Page
      • Landing Page Template
      • Snippet
      • Image
      • File

      Represents root-level folders found in the Marketing Activities path

      • Zone

      NOTE: Marketing Folder and Program folders indicate they exist in the Marketing Activities path.
    • folder_url
      • A direct url to the folder in Marketo
      • Not a universal link
      • Works properly when a user authenticates the folder URL
    • id: The ID of the folder
    • isArchive: Indicates whether the folder has been archived
    • isSystem: Indicates whether or not the folder is a system folder 
      Note: If this is set to True, then the folder itself is read-only. But the system can create children folders for it.
    • name: Name of the folder
    • parent
      • id: ID of the parent folder or program
      • type: Can be Folder or Program
    • path: Shows the folder’s hierarchy in the folder tree, similar to a Unix-style path  
      Note: The first entry in this field will always be Marketing Activities or Design Studio. If the target instance has workspaces, then the second entry in the path will be the name of the owning workspace. 
    • updatedAt: The date and time the folder was last updated
    • workspace: The workspace where you can locate the folder
  • State: Refer to this section to check if the module worked or failed 
    • Code: This is the success/error code that the module pulls from Smartsheet 
    • Message: A system message that the module returns from Smartsheet
      • For example, if the module couldn’t find an assignable, the message you might see in this field is “Not found”
    • Status: This is the status the module returns from Smartsheet 
      • These are examples of status labels you might encounter:
        • Succeeded - The system successfully found the value 
        • Failed - The system didn’t find the information

Find Folder by Name 

This module helps you search for a parent folder and get its ID to use it in other modules.

Find Folder By Name

Find Folder by Name field

Folder Name 

In this field, enter the name of the folder you’re searching for. 

When searching by name, note that both Marketing Activities and Design Studio are their own root folders. This means you can retrieve them by name, and use them to move the rest of the folder hierarchy to a destination instance. 

Once Bridge executes the Folder Name module in a workflow, you’ll see the following data groups: 

  • Data
    • accessZoneId
    • createdAt: The creation date and time 
    • description: The description of the folder 
    • folder
      • id: the ID for the folder
      • type: can be Folder or Program
    • folderType: Reflects the usage of the folder 

      Usage

      folderType

      Contains multiple types of assets

      • Marketing Folder
      • Program

      Contains only a that type of asset, subfolder, and template version of that UI type

      • Email
      • Email Template
      • Landing Page
      • Landing Page Template
      • Snippet
      • Image
      • File

      Represents root-level folders found in the Marketing Activities path

      • Zone

      Note: Marketing Folder and Program indicate that they exist in the Marketing Activities path.
    • folder_url
      • A direct url to the folder in Marketo 
      • Not a universal link 
      • Works properly when a user authenticates the folder URL
    • id: The ID of the folder 
    • isArchive: Indicates whether the folder has been archived 
    • isSystem: Indicates whether or not the folder is a system folder 
      Note: If this is set to true then the folder itself is read-only. But the system can create children folders for it. 
    • name: Name of the folder 
    • parent
      • id: ID of the parent folder or program 
      • type: Can be Folder or Program
    • path: Shows the folder’s hierarchy in the folder tree, similar to a Unix-style path  
      Note: The first entry in the path will always be Marketing Activities or Design Studio. If the target instance has workspaces, then the second entry in the path will be the name of the owning workspace. 
    • updatedAt: The date and time the folder was last updated 
    • workspace: The workspace where you can locate the folder
  • State: Refer to this section to check if the module worked or failed 
    • Code: This is the success/error that the module pulls from Smartsheet
    • Message: A system message that the module returns from Smartsheet
      • For example, if a module couldn’t find an assignable, the message you might see in this field is “Not found”
    • Status: This is the status the module returns from Smartsheet 
      • These are examples of status labels you might encounter: 
        • Succeeded - The module successfully found the value
        • Failed - The module didn’t find the information

Get Folder

This module works as a junction. It has a forked path depending on the outcome, which could be either of the two: 

  • Folder Found 
  • Folder Not Found 

Give the module a name when dragging it to a workflow.

Group Name

Bridge uses the group name as a reference in case you need to refer back to it in the latter part of the workflow. After adding it to the workflow, the module will look like this:

Get Folder

Folder ID field 

This is the ID for the folder you want to retrieve.

Folder ID data groups

The following data is available when the module has been executed in a workflow. Based on the outcome, the output will change as indicated below: 

Folder Found

  • Data
    • accessZoneId
    • createdAt: The creation date and time
    • description: The description of the folder 
    • folder
      • id: The ID for the folder
      • type: Can be Folder or Program
    • folderType: Reflects the usage of the folder 

      Usage

      folderType

      Contains multiple types of assets

      • Marketing Folder
      • Program

      Contains only a that type of asset, subfolder, and template version of that UI type

      • Email
      • Email Template
      • Landing Page
      • Landing Page Template
      • Snippet
      • Image
      • File

      Represents root-level folders found in the Marketing Activities path

      • Zone

      Note: Marketing Folder and Program indicate that they exist in the Marketing Activities path.
    • folder_url
      • A direct url to the folder in Marketo 
      • Not a universal link
      • Works properly when a user authenticates the folder URL
    • id: The ID of the folder 
    • isArchive: Indicates whether the folder has been archived 
    • isSystem: Indicates whether or not the folder is a system folder  
      Note: If this is set to True, then the folder itself is read-only. But the system can create children folders for it.
    • name: Name of the folder
    • parent
      • id: ID of the parent folder or program. 
      • type: Can be Folder or Program
    • path: Shows the folder’s hierarchy in the folder tree, similar to a Unix-style path  
      Note: The first entry in the path will always be Marketing Activities or Design Studio. If the target instance has workspaces, then the second entry in the path will be the name of the owning workspace. 
    • updatedAt: The date and time the folder was last updated 
    • workspace: The workspace the folder is contained in 
  • State: Refer to this section to check if the module worked or failed 
    • Code: This is the success/error code the module returns from Smartsheet
    • Message: A system message the module returns from Smartsheet
      • For example, if the module couldn’t find a value, the message might be “Not found”
    • Status: If the module found the folder you need, the status will be Succeeded

Folder Not Found

  • Data: In this data group, you’ll see the same fields you see when the outcome is Folder Found.
  • State: If the outcome is Folder Not Found, this is the information you’ll see:
    • Code: The value you’ll see in this field is “404”
      • Message: The message you’ll see in this field is “Folder does not exist with ID xxxxx”
      • Status: The value you’ll see in this field is Failed

Update Folder 

Use this module when you need Bridge to update a folder in Marketo after detecting the trigger you set up.

Update Folder

Update Folder fields

Folder ID: This is the ID for the folder you want to retrieve.

Customize Folder:

In this section, fill in these fields:

  • Folder Name: Update the name of the folder
  • Folder Description: Add description of your folder with up to 2,000 characters 
  • Archive Folder: Select this option to have the module archive the folder you referenced

These are the data groups you’ll see when the module executes the workflow:

  • Data
    • accessZoneId
    • createdAt: The creation date and time
    • description: The description of the folder
    • folder
      • id: the ID for the folder
      • type: Can be Folder or Program
    • folderType: Reflects the usage of the folder 

      Usage

      folderType

      Contains multiple types of assets

      • Marketing Folder
      • Program

      Contains only a that type of asset, subfolder, and template version of that UI type

      • Email
      • Email Template
      • Landing Page
      • Landing Page Template
      • Snippet
      • Image
      • File

      Represents root-level folders found in the Marketing Activities path

      • Zone

      Note: Marketing Folder and Program indicate that they exist in the Marketing Activities path.
    • folder_url
      • A direct url to the folder in Marketo 
      • Not a universal link
      • Works properly when a user authenticates it
    • id: The ID of the folder 
    • isArchive: Indicates whether the folder has been archived 
    • isSystem: Indicates whether or not the folder is a system folder.  
      Note: If this is set to True, then the folder itself is read-only. But the system can create children folders for it.
    • name: Name of the folder 
    • parent
      • id: ID of the parent folder or program 
      • type: Can be Folder or Program
    • path: Shows the folder’s hierarchy in the folder tree, similar to a Unix-style path  
      Note: The first entry in the path will always be Marketing Activities or Design Studio. If the target instance has workspaces, then the second entry in the path will be the name of the owning workspace. 
    • updatedAt: The date and time the folder was last updated 
    • workspace: The workspace where you can locate the folder 
  • State: Refer to this section to check if the module worked or failed 
    • Code: This is the success/error code that the module pulls from Smartsheet
    • Message: A system message that the module returns from Smartsheet 
      • For example, if a module couldn’t find a value, the message might be “Not found”
    • Status: This is the status a module returns from Smartsheet 
      • These are examples of status labels you might encounter: 
        • Succeeded - The system successfully found the value
        • Failed - The system didn’t find the information