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.

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.

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:

You’ll need:

For step-by-step API setup instructions, see Connecting to the Bonusly API.

For security, Bonusly only shows read/write access tokens once. If you lose a token, you’ll need to create a new one.

Use the token in the Authorization header:

The Bonusly Zapier integration supported a few common workflows. You can recreate each one with the Bonusly API.

Use Bonusly webhooks to listen for new recognition.

One thing to note: Zapier renamed a few fields before sending data to later Zap steps. If you move to the API directly, you’ll receive the raw Bonusly webhook payload instead. For example, fields like family_amount and child_count may appear differently than they did in Zapier.

Use Bonusly webhooks to listen for new achievement events.

The raw API payload may use slightly different field names than the Zapier version. For example, Zapier displayed the achievement user as receiver, while the API payload may use the underlying user field.

Use the Create a Bonus endpoint.

Your request can include details like the reason, receiver, amount, and hashtag.

Use the same Create a Bonus endpoint.

Instead of sending the amount, receiver, and hashtag as separate fields, include the full recognition message in the reason field, like:

Bonusly will parse the amount, receiver, and hashtag from the text.

Use the user autocomplete endpoint to look up a person by name or email.

This is helpful when your workflow needs to find a Bonusly user before giving recognition or matching data from another system.

Before turning off your Zap, test your API workflow with a small example.

We recommend checking that:

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.