This is the reference for the whole integration: the triggers that start a workflow, every piece of information they carry, and the six actions you can add.
The two triggers #
iDecide Finished
Fires whenever a viewer leaves the presentation, whether they reached the end or not. It sends their contact details and every choice they made along the way. You can filter it so the workflow only runs for one specific presentation.
iDecide Post A Link Started
Fires the moment a viewer enters their name and email on a Lead Capture link and clicks Watch. Because it fires before they have seen anything, it carries their contact details, but nothing about their choices.
Use iDecide Finished unless you have a specific reason not to. It gives you the contact details and the choices, where Post A Link Started gives you the contact details on their own.
What iDecide Finished carries #
| Field | What it tells you |
|---|---|
| iDecide, title | Which presentation was watched |
| Event Title |
A ready-made summary line, for example: "Jane Doe finished watching Presentation Test." Useful when you want one readable line rather than assembling it yourself |
| Date/Time Started | The date and time they clicked Play |
| Post A Link | Whether it came from a Lead Capture link or personalized link you created for them. It passes back True if the view came from a Lead Capture link. |
| Sender's name, sender user ID | Who sent it. Useful for tracking how many links each person on your team is sending |
| Viewer name, email, phone | Who watched it |
| Slides viewed | Which topics of the presentation they chose to see |
| Outcome | How they chose to move forward, for example: Schedule a Call or Buy Now |
| Viewer choices | Every answer they gave, as one line separated by commas |
| iDecide session ID | Identifies this one viewing. Other actions in the workflow use it |
| Finished | Returns "True" if they reached the end and chose an outcome, "false" if they left partway |
The six actions #
Create Personalized iDecide Link
Makes a link for the Contact in the workflow. The User you select is shown as the sender and receives the view notifications.
Create Post-A-Link iDecide
Makes a generic link that is not tied to a contact. The viewer enters their own details before starting. These are not recommended if you're sending a link directly to a specific contact.
Get Viewer Choice
Pulls one specific answer out of a view so a later step can use it. Returns the answer itself, and whether an answer was found at all.
Get Viewer Choice (Legacy)
This is an outdated version of Get Viewer Choice, kept only so existing workflows keep running. Do not use it in anything new.
Viewer Choice Condition
Branches the workflow by which option the viewer picked. Each branch's Selection Name has to match one of the answer options.
Multiple Choice Option Selected
For select all that apply questions. Gives you one value when a particular answer was picked and a different value when it was not.
Two fields that come up again and again #
User, static or dynamic
The Static option names one user as the sender, even if the automation is being run from someone else's account. So the user you selected sends everything from then on. Dynamic chooses the real sender at run time based on the User's account. We recommend using dynamic, set to User ID, so duplicate names cannot be confused.
iDecide Session ID
This ties each action to a specific view. This should always be the session belonging to the iDecide Finished trigger that started the workflow. You can select this field by choosing Custom Values, idecide, iDecide Finished, and selecting iDecide Session ID.
Tip: GoHighLevel connects to iDecide directly. There's no need to route it through Zapier.
Troubleshooting: GoHighLevel Questions and Fixes
