Important: You only need to create this token once. The same token can be reused across the whole organization. Keep the token value secure, because it may be needed again for future Zapier connections.

Create the Reachdesk campaign

Create the Reachdesk campaign you want Zapier to use for gifting.

Steps

1. In Reachdesk, go to the Campaigns tab.

2. Create the campaign you want to trigger from Zapier.

3. Set it up in the same way as any other Reachdesk campaign.

4. Copy the Campaign ID from the campaign URL.

   • Example: In https://app.reachdesk.com/campaigns/1503/settings, the Campaign ID is 1503.

Important: Do not use an Automated Campaign in Zapier. If you do, the send will charge the sender specified in the Zap instead of the connector user specified in the Automated Campaign.

Required fields for a send

To execute a send through Zapier, the app you connect to Reachdesk must provide the following fields.

Mandatory fields (All sends)

• Campaign Id

• Sender email

• Payment Currency

• Payment Wallet Type

• Review Process

• Recipient First Name

• Recipient Last Name

• Recipient Email

• Recipient Country

Additional fields (Required for physical gifts)

• Recipient Address Street 1

• Recipient City

• Recipient State/Region (Required for US/CA/AU)

• Recipient Postal Code/Zip Code

Understand the payment fields

The payment fields determine which wallet Reachdesk will charge for the send.

• Payment Currency: Determines which wallet currency will be charged. If empty, Reachdesk uses the campaign currency to look for the wallet.

• Payment Wallet Type: Determines whether Reachdesk should use a User Wallet or a Team Wallet. If empty, Reachdesk defaults to User.

• Sender Team: Determines which team wallet to use when Payment Wallet Type is Team. If the team is empty or does not exist, Reachdesk uses the Default team to look for the team wallet.

How Reachdesk selects the payment wallet

Reachdesk uses a combination of Payment Wallet Type, Payment Currency, and Sender Team (if populated) to determine which wallet to charge.

Additional wallet rules

When the wallet does not exist:

• User Wallet: Reachdesk automatically creates the user wallet.

• Team Wallet (Sender in Team): Reachdesk automatically creates the team wallet.

• Team Wallet (Sender NOT in Team): Reachdesk uses the sender’s User Wallet in the specified currency.

Example 1: User Wallet

• Payment wallet type = User
• Payment Currency = GBP
• Sender team = empty

Result: The payment wallet will be the Sending User's "User Wallet GBP"

Example 2: Team Wallet

• Payment wallet type = Team
• Payment Currency = GBP
• Sender team = Account Managers UK

Result: The payment wallet will be the Sending User's "Account Managers UK Team Wallet GBP"

Frequently Asked Questions

Can I use one API token for multiple Zaps? 

Yes. Once the API token has been created, you do not need to create another one for each Zap. One token can be used for the whole organization.

Can I use an Automated Campaign in Zapier? 

No. Do not use an Automated Campaign in Zapier. If you do, the send charges the sender specified in the Zap instead of the connector user specified in the Automated Campaign.

What happens if I leave Payment Currency blank? 

If Payment Currency is blank, Reachdesk uses the campaign currency to find the wallet.

What happens if I leave Payment Wallet Type blank? 

If Payment Wallet Type is blank, Reachdesk defaults to User and looks for a user wallet.

What happens if the team is blank or invalid? 

If the team is blank or does not exist, Reachdesk uses the Default team to look for the team wallet.

What happens if the selected wallet does not exist? 

Reachdesk handles this based on wallet type:

• For a User Wallet, Reachdesk creates the wallet automatically.

• For a Team Wallet, Reachdesk creates the wallet automatically only if the sender is part of that team. If the sender is not part of that team, Reachdesk uses the sender’s User Wallet in the specified currency.