In this article, we’ll show you how to connect your Marketo form to a Sequel event using a webhook. When someone submits your form or enters your Smart Campaign, they’ll be automatically registered for your Sequel event.
For a full overview of our Marketo integration, see our dedicated documentation.
In this article
• Create a custom field "Sequel_eventid"
• Create a Sequel webhook
• Create a Smart Campaign triggered by your form
• Set the event ID in your campaign Flow
1. Create a Custom Field "Sequel_eventid"
In Marketo, go to Admin > Data Management > Field Management.
Click "New Custom Field".
Fill in the following details:
Object: Person
Type: String
Name: Sequel_eventid
API Name: sequaleventid
This field will store the ID of the Sequel event you want to register leads to.
2. Create a Sequel Webhook
Go to Admin > Integration > Webhooks.
Click "New Webhook".
Fill in the form with:
Webhook Name: Sequel registration
URL:
https://api.introvoke.com/api/v3/events/{{lead.Sequel_eventid:default=edit me}}/registrantRequest Type: POST
Request Token Encoding: Form/Url
Template:
name={{lead.Full Name}}&email={{lead.Email Address}}
3. Create a Smart Campaign Triggered by Your Form
In Marketing Activities, select your program and click New > New Smart Campaign.
In the Smart List, add the trigger "Fills Out Form".
Select the Marketo form you want to use.
4. Set the Event ID in Your Flow
In the Flow tab, add a “Change Data Value” action:
Attribute: Sequel_eventid
New Value: paste your Sequel event ID here
(You can find it in the Event Summary inside Sequel.)
Add a “Call Webhook” action and choose the Register webhook you created.
Additional Notes
If you want to store the unique Sequel access link in Marketo, you can create a custom field and map
join_urlfrom the Sequel responseIf Sequel responds with 404, it means the event ID is incorrect. Double-check that the value in the Sequel_eventid field exactly matches your Sequel event ID.
If you receive a 500 error, make sure:
The Request Token Encoding is set to Form/Url
You do not have any JSON-related headers (such as Content-Type: application/json)