Moving from Zapier to the Bonusly API
Bonusly’s Zapier integration is no longer actively supported. If your team uses Zapier to connect Bonusly with other tools, you can keep building custom workflows with the Bonusly API instead.
The API gives your team more control over how data moves in and out of Bonusly. You can use it to give recognition, pull recognition data, look up users, and build custom workflows with the tools your team already uses.
This guide walks through the basics of moving common Zapier workflows to the Bonusly API. For more detail on creating API tokens and making requests, see our guide: Connecting to the Bonusly API.
What’s changing
The Bonusly Zapier integration is no longer actively supported.
Existing Zaps may continue to work, but we recommend moving any important workflows to the Bonusly API. This gives your team a more reliable way to maintain custom workflows over time.
Who should use the API
The Bonusly API is best for teams that have access to a developer, IT admin, or technical partner who can build and maintain custom workflows.
You might use the API to:
Give recognition from another internal tool
Pull recognition data into a reporting workflow
Connect Bonusly to an HRIS, intranet, or custom app
Build a custom automation that replaces an existing Zap
Before you start
You’ll need:
A Bonusly account — Global or Tech admin permissions for company-wide tokens, or any Bonusly account for tokens scoped to personal automation
A Personal Access Token (PAT) with the scopes your workflow needs
Someone comfortable working with REST APIs and JSON
Access to the tool or system you want to connect to Bonusly
Create an API access token
The Bonusly API uses Personal Access Tokens (PATs). For step-by-step setup instructions, see Connecting to the Bonusly API.
Open the right mint surface:
For a company-wide workflow** (anything that needs to act on data outside one user's own account), sign in as a Global or Tech admin and go to **Company → Integrations → API & Tokens**.
For a personal-automation workflow** (e.g. you're rebuilding a Zap that only ever ran on your own account), go to your own **Settings → Services** page. Any Bonusly user can mint a PAT here, scoped to what your role allows.
Click **Create token** (admin page) or **Generate** (Services page), give it a descriptive name, pick an expiration (up to one year), and select the scopes your workflow needs (e.g. `recognition:write` to give bonuses, `recognition:read` to pull recognition data, `user:read` to look up users).
Click **Create**. Bonusly will show the token string **once** — copy it into your integration before closing the dialog, then store it somewhere secure.
If you lose a token, you'll need to mint a new one. Tokens also expire — Bonusly emails the token owner 30 and 7 days before expiry so you can rotate before the workflow breaks.
If your Zap used “Find User”
We recommend checking that:
The PAT has the right scopes
Requests use the `Authorization: Bearer <token>` header
The workflow handles failed API responses
The workflow does not create duplicate recognition
The right person or system owns the PAT (token expiration reminder emails are sent to its owner)
Need help?
If you’re not sure how to replace your Zapier workflow, contact us at [email protected]. Include a short description of what your Zap does today, and we’ll point you toward the best API option.