This workflow creates a personalized presentation link for every new contact and emails it to them, without you writing the email or making the link. It is the simplest, yet most useful automation in the integration and it takes about five minutes to build.
Build the workflow #
- Go to Automation, click Create workflow, and start from scratch.
- Set the trigger to Contact Created, then save.
- Add the action Create Personalized iDecide Link.
- Choose the presentation you want to send.
- Set the User field: Click the three-dot dynamic input, choose User, then select User ID. Save the action.
- Add a Send Email action.
- Set From Name and From Email to the dynamic user values rather than typing your own address.
- Write your subject and body.
- Where the link should go, click Custom Values, scroll down to iDecide, open #1 Create Personalized iDecide Link, and choose URL.
One more step worth adding #
Create a Custom Contact Field called "iDecide Link" in your Contacts Settings. Then add an Update Contact Field action to your workflow after the link is created to write the URL into the custom field. Now, every email, text, and follow-up you send later can then pull that field instead of generating a new link.

Why User ID and never a name #
The User field can be set two ways. Static picks one person when you build the workflow, and that person is the sender on every run, no matter whose contact it is. On a team of six or a team of a hundred, every presentation goes out from the same name. Dynamic resolves the real sender each time the workflow runs, which is almost always what you want.
Within dynamic, choose User ID rather than User Full Name. If you have two people named John Doe, GoHighLevel and iDecide have no way to tell them apart, and the link gets attributed to the wrong person.
Tip: Storing the link on the contact means you create it once and reuse it everywhere. Without it, every message that mentions the presentation has to build a new link, and the contact ends up with several different ones.
Next: Example: Capturing Viewer Choices in GoHighLevel
