URL

The URL integration in Uncanny Automator allows you to trigger workflows when a specific URL with parameters is visited.

It’s useful for capturing user interactions, linking offline systems with your website, and initiating automations via unique links—without requiring forms, user input on the page, or code.

This integration includes two triggers and it works with both logged-in and anonymous site visitors.

What is a URL parameter?

A URL parameter is a piece of information added to the end of a URL to pass data to a website. They are commonly used to track campaign performance, capture data, or trigger specific responses on a page.

URL parameters follow a “?” in the URL and use a key-value structure. For example:

https://yoursite.com/?color=blue

In this case, “color” is the parameter name (i.e., key), and “blue” is the value.

A URL can have multiple parameters by simply including “&”. For example:

https://yoursite.com/?color=blue&campaign=summer

There are two types of URL parameters:

• GET parameters: These parameters are added directly to the end of a URL and are visible to anyone who looks at the address bar. These parameters are bookmarkable, shareable, less secure, and best for searches, filters, and/or campaigns.
• POST parameters: These parameters are sent “behind the scenes”, not in the URL. Front-end visitors will not see this data in the address bar, so it’s more private. These parameters are typically used for forms, file uploads, or for sending sensitive information such as passwords.

Uncanny Automator’s URL integration supports both GET and POST parameters.

Available triggers

The URL integration provides two triggers:

1. A user visits a URL with a URL parameter(s) set: This trigger runs when a logged-in user visits a URL that includes the parameter(s) you define in the trigger conditions. You can specify:
   • exact parameters that must be present (for example, “color=blue”)
   • whether any or all of the parameters must match

2. A URL with a URL parameter is visited: This trigger runs for any user, including anonymous visitors, when they visit a URL that includes the parameter(s) you define in the trigger conditions. You can specify:
   • exact parameters that must be present (for example, “color=blue”)
   • whether any or all of the parameters must match

You can use this trigger to run automations for logged-out users, which is useful for public pages or campaigns shared via email or social media.

Available tokens

Both triggers support the following tokens:

• URL visited: The full URL that the user or site visitor accessed, including parameters.
• All repeater parameters: The complete list of parameters specified in the trigger conditions. This allows you to pass dynamic data through the URL and use it in actions like sending emails, tagging users, or updating custom fields.

GET and POST parameters: The complete list of parameters specified in the trigger conditions, whether they are GET or POST.

Possible use cases

The URL integration unlocks very flexible and powerful automation scenarios. Here are just few examples:

1. Link Tracking and Attribution: Track how users and site visitors arrived on your site or which campaign led them there by including a unique URL parameter (for example, “ref=affiliate1”). Combine this with Automator actions like tagging logged-in users in your CRM or monitoring affiliate performance.
2. Personalized Onboarding: Send a unique onboarding link (for example, invite-client123) that triggers an automation to grant access to specific content or send a welcome message when the link is visited.
3. QR Code and Print Campaigns: Embed URLs with parameters in QR codes or printed materials. When scanned or visited, Automator can log the visit or perform follow-up actions—even for anonymous users.

Best practices

• Avoid tying sensitive functionality to URL triggers: URL‑based triggers are public and potentially shareable. Do not use them to control anything sensitive—such as granting membership access, logging users in, or triggering financial transactions.
• Implement throttling/rate‑limiting: URL clicks or calls may be triggered repeatedly (such as bots hitting the URL). If you’re concerned about rate limits, use Automator’s Throttle feature to restrict the number of times within a period the recipe can be triggered.