Rollbar integration

What it does

The Rollbar integration lets your agency send occurrences into a client's Rollbar project, look up and triage items, read occurrences and item history, record and finish deploys, and pull the project's most active errors for a daily digest. Its triggers fire in real time when Rollbar sees a new item, reactivates or resolves one, a person reopens one, an item crosses an occurrence milestone, an error occurs, or a deploy is reported.

Connect a Rollbar account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Rollbar and click Connect.
3. In a new tab, sign in to rollbar.com and open the client project you want to integrate.
4. Open Project Settings, then Access Tokens, and create or copy a token with the read, write and post_server_item scopes.
5. Paste the token into TaskJuice and save the connection.

Each scope backs a specific part of the integration:

To rotate or revoke the token later, return to the project's Access Tokens screen, regenerate the token, and update the TaskJuice connection. Use a separate token per client project so revocation stays scoped.

Triggers

Every trigger has an optional Environment filter. Pick one (for example production) to ignore events from other environments, or leave it empty to receive them all.

You do not set these up in Rollbar yourself. When you publish a workflow, TaskJuice adds a webhook notification rule for that event to the project through the Rollbar API, pointed at your own delivery address. Your project's existing notification rules and its default webhook URL are left untouched. Removing the Rollbar connection deletes the rules TaskJuice added.

New Occurrence fires once for every error your application reports. On a busy project that is a run per error, so prefer New Item or Item Occurrence Milestone unless you really need every event.

Actions

Items

• rollbar/track-occurrence reports an error or message to the project, with environment, level, code version, custom data and an optional person.
• rollbar/list-items pages through items, filtered by status, level, environment, framework and assignee.
• rollbar/get-item fetches one item by its ID.
• rollbar/find-item finds an item by its project counter (the number in the item's Rollbar URL) or by an occurrence UUID.
• rollbar/update-item-status resolves, mutes, archives or reactivates an item, changes its level or assignee, and records the version that resolved it.
• rollbar/list-item-events reads an item's history: comments and status, level, assignment and title changes.

Occurrences

• rollbar/list-item-occurrences lists one item's occurrences, newest first.
• rollbar/list-occurrences lists the latest occurrences across the whole project.
• rollbar/get-occurrence fetches one occurrence with its full stack trace, request and person data.

Deploys

• rollbar/report-deploy records a deploy against an environment and revision.
• rollbar/update-deploy finishes a deploy that was reported as started, marking it succeeded, failed or timed out.
• rollbar/get-deploy fetches one deploy by ID.
• rollbar/list-deploys pages through recent deploys.

Reports

• rollbar/get-top-active-items returns the most active items over the last few hours with hourly counts, ready for a daily digest.

Known limitations

• A project access token reaches one Rollbar project. Connect each client project separately.
• Keep the project's webhook notifications turned on in Rollbar (Project Settings, Notifications, Webhook). If they are off, turn them on with any URL; the rules TaskJuice adds carry their own delivery address.
• The high occurrence rate event is not offered as a trigger, because Rollbar requires a per-rule rate threshold for it. Use Item Occurrence Milestone, or Get Top Active Items on a schedule.
• Project, team, user and access-token administration need an account access token and are not part of this integration.
• Rollbar may retry a delivery that takes longer than three seconds to acknowledge, so a workflow can occasionally run twice for one event.
• Update Deploy only works while the deploy is still started; Rollbar refuses later changes with a conflict error.