Skip to main content
Trigger links in the HoopAI platform allow you to start a workflow when a contact clicks a URL. By adding query string parameters to the trigger link, you can pass additional data into the workflow — such as a product name, source campaign, or custom field value.

​
Query string syntax

A query string begins with ? after the base trigger link URL, with each parameter formatted as key=value. Multiple parameters are separated by &. 
https://yoursubdomain.hoopai.com/trigger/abc123?source=email&product=starter
PartExamplePurpose
Base URLhttps://yoursubdomain.hoopai.com/trigger/abc123The trigger link generated by Hoop
?First separatorMarks the start of the query string
key=valuesource=emailA single parameter
&Between parametersSeparates multiple parameters
1

Create a new workflow

Go to Automation > Workflows in the Hoop platform and create a new workflow. Select Trigger Link as the workflow trigger.
2

Copy the trigger link URL

After saving the trigger, Hoop generates a unique URL. Copy this URL — it is the base URL you will append query strings to.
3

Append your query parameters

Add your parameters after the URL. For example, if your trigger link is https://yoursubdomain.hoopai.com/trigger/abc123, you can add ?utm_source=facebook&offer=premium to pass those values into the workflow.

​
Step 2: Use query string values in the workflow

1

Access the values in workflow actions

In any workflow action, you can reference query string values using the custom values picker. Look for Trigger Link in the values list — each query parameter you passed will be available as a selectable value.
2

Map values to contact fields

Use an Update Contact action to save query string values to contact custom fields. For example, map {{trigger_link.source}} to a custom field called “Lead Source.”
3

Use values in conditional logic

Add an If/Else branch that checks a query string value. For example, route contacts to different follow-up sequences based on {{trigger_link.product}}.
Name your query parameters descriptively — use product_interest instead of p so your workflow logic is easy to understand months later.

​
Passing dynamic values

You can insert dynamic contact data into trigger link query strings when sending them via email or SMS from Hoop. 
https://yoursubdomain.hoopai.com/trigger/abc123?email={{contact.email}}&name={{contact.first_name}}
Dynamic values like {{contact.email}} are resolved at send time. The contact receives a URL with their actual data filled in, not the placeholder text.

​
URL encoding

Special characters in query string values must be URL-encoded to work correctly.
CharacterEncoded formExample
Space%20 or +name=Jane%20Doe
&%26company=Smith%26Co
=%3Dcode=A%3D1
@%40email=jane%40example.com
If you do not encode special characters, your query string will break. For example, an unencoded & in a value will be interpreted as a parameter separator, splitting your data incorrectly.

​
Common formatting mistakes

The ? character should only appear once in the URL, right before the first parameter. Additional parameters use & as a separator. A URL like ?source=email?product=starter will not parse correctly.
Spaces in URLs cause errors. Use %20 or + for spaces in values, and avoid spaces in parameter names entirely. Use underscores instead: product_name=starter.
A parameter like source= with no value will pass an empty string into your workflow. This can cause issues with conditional logic that checks for specific values. Always provide a value for each parameter.
Query parameter names are case-sensitive. Source=email and source=email are treated as different parameters. Be consistent with casing across your trigger links and workflow logic.
1

Open the link in an incognito window

Paste the full trigger link with query parameters into an incognito browser window. This simulates a contact clicking the link without any cached session interfering.
2

Check the workflow execution log

After clicking the link, go to Automation > Workflows and open your workflow. Check the execution history to confirm the workflow was triggered and that query string values were captured correctly.
3

Verify contact data

If your workflow maps query string values to contact fields, open the contact record and confirm the fields were updated with the expected values.
Last modified on March 5, 2026