The Reachdesk app in Zapier allows you to connect up to other apps to trigger a Reachdesk e-gift or physical gift send. Before you create your first zap (workflow), there are a few things you need to do:

If this is your first time integrating Reachdesk with Zapier, you'll need a Reachdesk admin (any user of yours with admin privileges) to create a new API token. Head into Reachdesk > Organisation > Settings > API tokens and create a new token, call it Zapier (or whatever makes sense to you).

https://app.reachdesk.com/organization/api_tokens

Copy that token down somewhere you'll need it when creating a zap. Note: Once a token has been created, you won't need to create any more to connect Reachdesk to Zapier; you can use one token for the whole organisation (so keep the token value safe for re-use!)

Create the Reachdesk campaign that you'd like to use to trigger a gift - this should be created in the campaigns section. It should follow the same format as all other campaigns.

• Note: Your campaign ID is found by going into the Reachdesk campaign you'd like to send, and grabbing the number in the URL. Ie: https://app.reachdesk.com/campaigns/1503/settings.

  Note:  Please do not use a Triggered Campaign in Zapier. This will charge the sender specified in the zap instead of the connector user specified in the Triggered Campaign.

   

Campaign Id, Sender email, Payment Currency, Payment Wallet Type, Review Process, Recipient First Name, Last Name, Email and Country. The app that you're connecting to Reachdesk will need to pull those fields in, in order to execute a send.

Important Information about payment fields

1. Payment Currency

This will determine which currency of the payment wallet will be charged for the send so it is very important that this is setup correctly.

2. Payment Wallet Type

This will determine whether you want to use a User Wallet or Team Wallet.

3. Sender Team

This will determine the specific "team" related to the team wallet that you want to use to pay for your sends.

How do we determine the payment wallet that is used:

We will use a combination of the Payment Wallet Team, Payment Currency and the Sender Team (if populated) to select the Payment Wallet.

Other conditions:

• If the Payment Currency is empty, we will use the campaign's currency to look for the wallet.

• If the Payment Wallet Type is empty, we will use "User" as the default and look for a user wallet.
• If the Team is empty or it does not exist, we will use the "Default team" to look for the team wallet.
• If the Payment Wallet does not exist:
  • If it's a user wallet, we will automatically create the user wallet
  • If it's a team wallet and the sender is part of the team, we will automatically create the team wallet
  • If it's a team wallet and the sender is NOT part of the team, we will use the user’s wallet with the specified currency

Examples:

Example 1:

• Payment wallet type = User
• Payment Currency = GBP
• Sender team = empty
• The payment wallet will be the Sending User's "User Wallet GBP"

Example 2:

• Payment wallet type = Team
• Payment Currency = GBP
• Sender team = Account Managers UK
• The payment wallet will be the Sending User's "Account Managers UK Team Wallet GBP"

For more details on how to use your Zapier integration to send, see our help articles:

Integrate Reachdesk with Influitive via Zapier to send e-gift cards

Integrate Reachdesk with Influitive via Zapier to send physical gifts