How to connect Sentry to Fareeqy and turn errors into tasks

What this integration does

Every new error Sentry catches in your app reaches Fareeqy as a task, so it is followed up in the same place your team plans and does its work, instead of staying in a tool only developers open.

• One error becomes one task however often it repeats, so the list never fills with copies of the same error.
• Tasks land in one task list per week inside the project you choose, named by its date range. The week starts on Saturday.
• When the error is resolved in Sentry, the task completes in Fareeqy, with a comment naming who resolved it.
• When you complete the task in Fareeqy, the error is resolved in Sentry. Reopening the task does not reopen the error there.
• The error's page in Sentry shows a link that opens its task in Fareeqy.
• If the error comes back after being resolved, the same task reopens with a comment saying so, instead of a duplicate being created.
• When the error is assigned in Sentry, the task is assigned to the project member with the same email in Fareeqy.
• If you delete a task, Fareeqy does not recreate it when the error repeats.

Before you start

• Integrations are connected by the company owner, or by a member whose role grants the “Manage integrations” permission.
• In Sentry, you need permission to install integrations in your organization (usually Owner or Manager).
• Each plan includes a number of integrations. The free plan includes one.
• A Sentry organization connects to Fareeqy once. If yours is already connected, the Sentry card shows Cancel integration instead of Start integration.

What Fareeqy asks for in Sentry

• Issue & Event (Read & Write): to read an error and turn it into a task, to resolve it when its task is completed, and to put the task's link on its page.
• Organization (Read & Write): for one thing only, so Fareeqy can remove its app from Sentry when you disconnect from Fareeqy.

How to connect

1. Open Company Settings, then Integrations.
2. On the Sentry card, click Start integration. A Sentry page opens.
3. Choose your Sentry organization if you have more than one, then click Accept & Install.
4. You return to Fareeqy, on the page that asks where Sentry errors should land.
5. Choose New project to have Fareeqy create a project for Sentry errors, or Existing project and pick one from the list.
6. Optional: set a default assignee. Errors with no assignee in Sentry who belongs to the project go to them.
7. Click Finish. The next new error that arrives appears as a task in the project.

Tip: You can also start from Sentry: under Settings, then Integrations, search for Fareeqy and click Install. After approving, you move to Fareeqy, sign in, and choose the project the same way.

Note: There is no URL or key to copy. The whole connection is an approval inside Sentry and a project choice inside Fareeqy.

Tip: Sentry sends every new error from every environment, staging included. To receive production errors only, create an Alert Rule in Sentry that filters on the production environment, and set Fareeqy as its action.

Connected, but nothing arrived?

On the Integrations page, click the delivery log next to the integration. It shows everything that arrived from Sentry and what Fareeqy did with it: a task was created, an existing task was updated, or nothing changed and why. A row marked Processing finishes within seconds. Filter to ignored and rejected to see only what did not become a task.

• “Needs a destination”: the project or task list was deleted, or the project was archived. Open Manage and choose another project.
• The task has no assignee: the developer's email in Sentry does not match any project member's email. The log names the email.
• “You have reached the number of integrations in your plan”: disconnect another integration, or upgrade your plan.
• “The connection with Sentry did not complete”: start again from Start integration, and if it repeats, email support@fareeqy.com.

Edit or disconnect

• From Manage, change the project or the default assignee at any time.
• Click Disconnect next to the integration, or Cancel integration on the Sentry card. New errors stop arriving and Fareeqy's app is removed from Sentry. Tasks already created stay as they are.
• If Fareeqy cannot remove the app from Sentry, the message tells you so. Remove it yourself under Settings, then Integrations, in Sentry.
• Uninstalling Fareeqy from inside Sentry disconnects it in Fareeqy too.
• A disconnected integration stays on the page with its log. Click Reconnect to bring it back while the app is still installed in Sentry, or Delete integration to remove it with its log. The tasks it created stay in their projects.
• The project an integration delivers to cannot be deleted while it is connected. Disconnect it or point it at another project first.

Changelog

• September 30, 2026: completing a task in Fareeqy resolves its error in Sentry, and the error's page in Sentry links to its task. Disconnecting from Fareeqy removes the app from Sentry, and a disconnected integration can be deleted with its log.
• September 28, 2026: first release. New errors become tasks, with resolve, reopen and assignment sync.

The result? Your app's errors are followed up like any other work in Fareeqy: each has an owner and a status, and closes when it is fixed.