Incoming Button Click

Trigger identifier: incoming_button_click.

Receives the signed links produced by Generate Resolution Buttons. Its output tells the workflow which ticket and choice the link represents. The trigger itself does not update HubSpot status.

Configure the pair

1. Install this trigger using the HubSpot connection configured for your workflow.

2. Provide the installed trigger's subscription ID to Generate Resolution Buttons and use the same connection for both.

3. Verify the generated links use the intended public workflow-server host.

4. Insert the generated html into the intended outgoing message.

5. Build the receiving workflow: Get Ticket → validate current ownership/state → branch on resolution → update the correct pipeline stage.

6. Test the complete workflow with a test ticket before distributing links.

Trigger options

Field	Default	Use
close_ticket_html	Built-in confirmation page	Page returned for resolution: true
keep_ticket_html	Built-in acknowledgement page	Page returned for resolution: false
expired_link_html	Built-in expiry page	Page shown for an expired link

Templates may include {ticket_id}. They use Python-style format substitution; escape literal braces in custom CSS as {{ and }}. Keep landing-page wording consistent with what your receiving workflow can actually establish. A rendered page is not verification that an asynchronous ticket update succeeded.

Output

Field	Type	Meaning
ticket_id	string	Ticket identified by the signed link
resolution	boolean	true for the resolve choice; false for continued help

Safe use

Share generated links only with the intended recipient and keep them out of shared documentation and logs. A link confirms a ticket-related choice; it does not verify the person's identity.

Before applying a change, check the ticket's current state and the permissions required by your business process. Ensure repeated handling does not cause unintended changes. Use additional identity verification or human review when needed.

The receiving workflow performs the ticket update. Confirm the result in HubSpot; the landing page alone is not confirmation that the update succeeded.