Refficks partner work in Pabbly Connect
Partner work in Pabbly Connect: be told when something happens in Refficks, and add partners, links and codes from a workflow. Sales still come from your payment provider.
What it gives you
- A workflow in Pabbly Connect that runs when a partner applies, is approved, earns a commission or is paid, among other events.
- Partners, programme places, links and codes made from Pabbly Connect, each in History under the key that made it.
What it does not
- It does not report sales. Sales come from your payment provider or store, which Refficks hears from directly; a sale reported from a workflow as well would count twice, so the key cannot do it.
- Partners it adds arrive as applicants, and approving them, choosing their tier or suspending them is done in Refficks by a person.
- The signature cannot be checked in Pabbly Connect, so anybody who learns the webhook URL can start the workflow.
Steps
1. Make a Pabbly Connect key
In Refficks, open Integrations and, on the automation card, press "Make a key for Pabbly Connect". Copy the key it shows: it is shown once, and Refficks keeps only enough of it to recognise.
This key can read partners, programmes, links and money, add partners, add them to programmes, and make links and codes. It cannot report a sale, approve an applicant, choose a tier or suspend anybody, so nothing a workflow does with it changes what a partner is paid.
2. Be told when something happens
In Pabbly Connect, start a workflow with Webhook by Pabbly as the trigger app and Catch Webhook as its event, and copy the webhook URL it shows.
In Refficks, open Integrations → Webhooks, paste that address, tick the events the workflow should hear about, and add the endpoint. Copy the signing secret it shows once.
Refficks sends only to https:// addresses that resolve to the public internet, and tries a failed delivery five times over about an hour before pausing the endpoint and telling you.
3. Check that a delivery came from Refficks
Every delivery carries an X-Refficks-Signature header, t=<seconds>,v1=<signature>, where the signature is HMAC-SHA256 of "<seconds>.<raw body>" under the signing secret, written in hex.
Pabbly Connect describes no step that can check a signature, and its trigger hands the body on already taken apart, so the signature cannot be checked there. Treat the webhook URL as the secret: share it with nobody, and if it leaks, delete the endpoint in Refficks and make a new webhook in Pabbly. A forged delivery can only start your workflow, and the key cannot do anything that changes what a partner is paid.
4. Add partners, links and codes
In Pabbly Connect, add an API by Pabbly action, choose POST, paste the address below as the endpoint URL, give your key as a bearer token (or a header Authorization: Bearer <your key>), and put the JSON body in the data section.
Send it to https://go.refficks.com/api/v1/server with the key as a bearer token. POST /partners with an email (and a name if you have one) adds a partner, who arrives as an applicant for you to approve in Refficks. Once approved, POST /programs/{program}/partners with partner_id adds them to a programme, and POST /tracking-links or POST /coupon-codes with program_id and partner_id makes their link or code.
A partner added this way sends no "Partner applied" delivery, because nobody applied. Approving them in Refficks sends "Partner approved", which another workflow can listen for to make their link.
A refusal comes back as JSON with error.message saying why, such as an applicant who has not been approved yet.
Sources
Have an account? Open this guide in Refficks for your own script and the checks that show when it is working. New to Refficks? Create an account.