Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Marketo location.
marketo_api.png

Marketo

Create a Marketo Destination​

  1. Click the + icon on the Nexset that will be sent to the Marketo destination, and select the Send to Destination option from the menu.

  2. Select the Marketo connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Marketo account, and click Next; or, create a new Marketo credential for use in this flow.

  3. In Nexla, Marketo destinations can be created using pre-built endpoint templates, which expedite destination setup for common Marketo endpoints. Each template is designed specifically for the corresponding Marketo endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Marketo destinations can also be configured manually, allowing you to send data to Marketo endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Marketo endpoints. Each template is designed specifically for the corresponding Marketo endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create or Update records of Type

    This endpoint template creates or updates records of a specific resource type in your Marketo account, such as Leads, Companies, Opportunities, or Custom Objects. Use this template when you need to create new records or update existing records in Marketo from your data flow. The endpoint supports batch mode, allowing you to send multiple records in a single request.

    • Enter the resource type in the Resource Type field. This should be the name of the Marketo resource you want to create or update, such as leads, companies, opportunities, or customobjects. The resource type is used to construct the API endpoint URL (e.g., {rest_api_endpoint_url}/v1/leads). Ensure you use the exact resource type name as defined in the Marketo API.

    This endpoint sends data as JSON in the request body to create or update records in Marketo. The endpoint supports batch mode, allowing you to send up to 300 records per request. The data structure must match the Marketo API's expected format for the specified resource type. Ensure your data flow provides the required fields for the resource type you're creating or updating.

    For detailed information about available resource types, required fields, data formats, and record schemas, see the Marketo REST API endpoint reference.

Configure Manually​

Marketo destinations can be manually configured to send data to any valid Marketo API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Marketo destinations, such as destinations that send data to multiple endpoints or destinations that require custom request headers or parameters.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Marketo API from the Method pulldown menu. Marketo API typically uses POST method for creating or updating records.

API Endpoint URL​

  1. Enter the URL of the Marketo API endpoint to which data will be sent in the Set API URL field. This should be the complete URL including your Marketo REST API Endpoint URL (from your credential), the API version (/v1/), and the resource type (e.g., {rest_api_endpoint_url}/v1/leads).

Ensure the API endpoint URL is correct and accessible with your current credentials. The Marketo API endpoint URL should point to the specific resource type you want to create or update. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Marketo API. The request body should contain the data to be created or updated in Marketo, formatted as JSON. The request body format is typically {message.json} which sends the entire Nexset data as JSON, or you can use a transform function to format the data as an array of records for batch operations.

The request body must be valid JSON and must match the Marketo API's expected format for the specified resource type. For batch operations, the data should be formatted as an array of record objects. Ensure your data flow provides the required fields for the resource type you're creating or updating. The data structure must match the Marketo API's expected format. For detailed information about required fields and data formats, see the Marketo REST API endpoint reference.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.