Buttons

Buttons are a Pro feature.

Most triggers wait for something the site does. This one waits for a person to decide.

Put a button on any page. When somebody clicks it, the automation runs for them.

Setting one up

1. Add the A user clicks a button trigger.
2. Give it a key — any name you like, such as enrol-me.
3. Put the matching shortcode where you want the button:

[zapify_button key="enrol-me" label="Enrol me"]

Or as an inline link:

[zapify_link key="enrol-me"]Claim your badge[/zapify_link]

The key is what ties the two together.

Why a key and not an automation number

Because the number changes and the key does not.

Automation IDs are local to one site. Export an automation and import it somewhere else and it arrives with a different ID; copy a page from staging to production and a shortcode with an ID in it now points at a different automation, or at nothing. A key you chose travels with both halves.

[zapify_button automation="12"] is accepted for the single-site case, but the key is the thing that survives a migration.

Who can click

Logged-in visitors. The run is attributed to whoever clicked, so per-user limits work exactly as they do everywhere else.

A logged-out visitor sees the button with Log in to do this instead of a page with a hole in it.

What it is not

The button is a form, not a link, and that is on purpose. A link that starts an automation gets followed by browsers prefetching, by scanners, and by cache warmers — none of which asked the visitor first.

Each button's security token is scoped to its own key, so a token minted for one button is not a ticket for another.