What Referly can do in Zapier
The Referly app on Zapier has three kinds of steps: triggers (Referly tells Zapier something happened), actions (Zapier changes something in Referly), and searches (Zapier looks something up in Referly).Triggers
A trigger is the first step of a Zap. These are the nine events Referly can announce:Actions
An action is a step that changes something in Referly:Searches
A search finds a record and hands its details to the next step. It doesn’t change anything:What Zapier can and can’t track
This is the part people get wrong most often, so it’s worth being blunt about it.Before you start
Check your plan
Have an affiliate program set up
Install the tracking script
Step 1: Create a Zapier account
Skip this if you already have one.Go to zapier.com
zapier.com in your browser and select Sign up.Create the account
Choose a plan
Step 2: Connect Referly to Zapier
The connection is made from inside Zapier, and Zapier sends you to Referly to approve it. You can start it from the Zap editor when you first pick Referly as a step, which is what most people do.Add a Referly step in Zapier
Referly in the app picker and select it.Select Sign in
Log in to Referly
Choose the program
Confirm
Back to Zapier
Step 3: Build a Zap that starts in Referly
This is the simpler direction: something happens in Referly, another app reacts.Pick the trigger app
Referly as the trigger app.Pick the trigger event
Choose the connection
Test the trigger
Add the action
Map the fields
Test and publish
Step 4: Send data into Referly
The other direction — something happens elsewhere and Zapier records it in Referly — takes one extra piece of work: telling Referly which affiliate deserves the credit.Get the affiliate ID out of your website
When a visitor arrives from an affiliate link likeyourwebsite.com/?ref=janedoe, the tracking script stores who sent them and puts two values on the page for you to use:
window.affiliateId— the ID of that specific click. This is the most accurate value, because it ties the sale to one visit.window.affiliateRef— the affiliate’s link name,janedoein the example above.
- Forms (Typeform, Jotform, Gravity Forms, HubSpot forms and similar) — add a hidden field, and set its value from
window.affiliateIdwhen the page loads. Every one of these tools documents hidden fields; search their help centre for “hidden field”. - Checkout and billing tools — most let you attach your own reference or metadata to a customer or an order. Put the value there.
- Course and membership platforms — look for custom fields on the member record.
Record a referral or a free trial
Use this when someone signs up, starts a trial, or books a demo, and no money has been taken yet.Add the action
Referly, and pick Create Referral.Fill in who the customer is
Add your own reference
Say which affiliate to credit
Add the plan, if it helps
Pro trial. It shows on the customer’s record. Leave it blank and Referly stores N/A.Test
Record a sale
Use this when money is actually taken. Referly works out the commission itself.Add the action
Referly, and pick Create Sale.Fill in the customer and amount
Say which affiliate or customer to credit
Add your invoice reference
Override the rate, only if you need to
Test
Example: post to Slack when a sale comes in
A good first Zap, because nothing can go wrong in Referly.- Trigger — Referly, New Sale Created.
- Action — Slack, Send Channel Message.
- In the message, mix your own words with values from the trigger: the affiliate’s first name, the customer’s name, the sale total, and the commission earned.
- Test, then publish.
Example: add new affiliates to your email list
- Trigger — Referly, New Affiliate Created.
- Action — your email tool, its “add or update subscriber” event.
- Map the affiliate’s email, first name, and last name. Most tools let you also store the affiliate link, which is handy for personalised onboarding emails.
- Test, then publish.
Example: record a sale from a checkout Referly doesn’t support natively
- Make sure the tracking script is on your site and the affiliate value reaches your checkout, as described above.
- Trigger — your checkout tool, its “new payment” or “order paid” event.
- Action — Referly, Create Sale. Map the customer’s name, email, and the amount, and put the affiliate value into Referral ID.
- Test with a real, small purchase, then publish.
Field reference
Required fields are marked. Everything else is optional.Create Affiliate
Update Affiliate
Create Referral
Update Referral
Create Sale
Update Sale
Find Affiliate, Find Referral, Find Sale
Delete Affiliate, Delete Referral, Delete Sale
Each takes the record’s ID and a Confirm Deletion field, so a mis-mapped Zap can’t quietly wipe records. Deletions can’t be undone.What Referly sends when a Zap triggers
Affiliate triggers hand over the affiliate’s name, email, status, commission rate, affiliate links, promo codes, totals for referrals, clicks, revenue and commission earned, and their commission plan and tier. Referral triggers hand over the customer’s name and email, your external user ID, their status and plan, total revenue and total commission generated, the landing page they arrived on, and a nested block with the affiliate’s details. Sale triggers hand over the amount, commission rate, commission earned, your external invoice and sale references, the products bought, whether a payout has been created, and nested blocks with the affiliate and the referred customer. Delete triggers only hand over the record’s ID — the record is already gone, so there’s nothing else to send.Testing your Zap
Test the whole path, not just the steps.- Test with a real affiliate link. Open your site through
yourwebsite.com/?ref=plus a real affiliate’s link name, in a private browsing window, then go through the sign-up or checkout as a customer would. This is the only way to know the affiliate value is being carried through. - Check both sides. After the Zap runs, look at the affiliate in Referly and confirm the referral or sale is on their record with the right commission.
- Use Zap history. Zapier’s Zap history shows every run, the data that came in, and the exact error if a step failed. It’s the first place to look when something doesn’t arrive.
- Delete your test records. Test referrals and sales count towards your plan’s limits and skew your reporting. Remove them once you’re happy.
Limits to plan around
How often a Zap can write to Referly. To keep things fast for everyone, Referly limits how many requests a connection can make: 100 a minute for reading, 30 a minute for creating, updating, or deleting, and 20 every fifteen minutes for anything to do with sales. Going over doesn’t break the connection — the request is refused and Zapier retries — but it does mean Zapier is the wrong tool for importing thousands of historical records. Use the import tools for that instead. Your Referly plan’s limits. Affiliates and referred customers created by a Zap count towards the same limits as ones created any other way. Once you’re at the limit, the step fails with a message saying so. Zapier’s task allowance. Every action step that runs successfully spends a task. A busy program can get through a free plan’s monthly allowance in a couple of days. One program per connection. A connection can’t reach across programs. No two-way syncing. Two Zaps pointed at each other will loop. If you create affiliates in Referly from another tool and also push Referly affiliates back to it, add a filter step so each Zap ignores records that came from the other one.Troubleshooting
The connection is refused when I try to sign in
The connection is refused when I try to sign in
Create Referral fails with an affiliate error
Create Referral fails with an affiliate error
Create Sale fails saying an amount is required
Create Sale fails saying an amount is required
The sale was recorded but no commission was given
The sale was recorded but no commission was given
Create Affiliate says the affiliate already exists
Create Affiliate says the affiliate already exists
My Zap triggers twice for the same sale
My Zap triggers twice for the same sale
Nothing happens when I create a test record
Nothing happens when I create a test record