Before you build the Zap
Create a Reachdesk API token
If this is your first time connecting Reachdesk to Zapier, a Reachdesk user with Admin permissions must create an API token.
Go to Organization > Settings > API Tokens.
Create a new token and give it a name like "Zapier" or "Zapier/GoToWebinar."
Save the token value somewhere secure. You will need it when you connect Reachdesk in Zapier.
Important: You only need one API token to connect Reachdesk to Zapier for your whole organization. Keep the token safe so it can be reused.
Create the Reachdesk campaign
Create the Reachdesk campaign you want to send to webinar registrants or attendees.
Note: You must create this as a Manual Campaign, not a Triggered Campaign. The campaign should be set up in the same way as your other manual Reachdesk campaigns.
Create a test registrant or attendee
Before testing the Zap, create a test record for yourself as a webinar registrant or attendee in GoToWebinar. This makes it easier to verify that the Zap is pulling through the correct test data.
Set up the Zap
We've created a ready-made Zap for you to set up your integration in a few minutes.
Add the GoToWebinar trigger
In Zapier, choose:
App: GoToWebinar
Trigger event: New Registrant or New Attendee
Then:
Select your GoToWebinar account.
Choose the webinar trigger you want to use.
Run the trigger test. You should see the test record you created earlier.
Add filters or flow controls (Optional)
After the trigger step, you can add extra filters in Zapier.
Add the Reachdesk action
Add the action step in Zapier:
App: Reachdesk
Action: Send eGift or physical gift
Then select your existing Reachdesk account or connect a new one.
Connect Reachdesk to Zapier
If you are connecting Reachdesk for the first time, use the API token you created earlier. When prompted in Zapier, paste the token into the API key field to authorize the connection.
Configure the Reachdesk action
Once Reachdesk is connected, complete the action fields in Zapier.
Add the campaign ID
Enter the Reachdesk campaign ID for the campaign you want to send. You can find this in the campaign URL.
For example, in https://app.reachdesk.com/campaigns/1503/settings, the campaign ID is 1503.
Add the sender email address
Enter the sender email address for the Reachdesk user the gift should send from.
Important: The sender email address must belong to an active Reachdesk user. That user must have access to the campaign and a funded wallet in the correct currency. If multiple users need to send the same campaign, each user must create their own Zap so sends are made from their own Reachdesk user account.
Map the recipient fields
Map the matching GoToWebinar fields into Reachdesk:
Recipient first name (Required)
Recipient last name (Required)
Recipient email (Required)
Company name (Optional)
Choose the send approval setting
Decide how sends should be handled in Reachdesk:
Auto-approve sends: The send will be processed automatically with no manual review.
Require review before sending: The sender will be notified when a new send is pending. The sender must then log in to Reachdesk to approve or reject the send.
Test and turn on the Zap
After you finish configuring the Zap:
Run a test in Zapier.
Confirm the test send appears in the Reachdesk Sends tab.
Turn on the Zap.
Your Reachdesk sends will now trigger automatically for new GoToWebinar registrants or attendees.
Frequently Asked Questions
Do I need a new API token for every Zap?
No. You can use one Reachdesk API token for the whole organization.
Should I create this as a manual campaign or an automated campaign?
Create it as a manual campaign. Because Zapier is "automating" the action from outside Reachdesk, the platform treats it as a manual send via API.
What sender email should I use?
Use the email address of a Reachdesk user who has permissions to send that campaign and has enough budget in their wallet.
Can multiple users send the same campaign through Zapier?
Yes, but each user must set up their own Zap if they want sends to come from their own account.
Comments
0 comments
Please sign in to leave a comment.