Skip to content

HomeDocsUsing ReqioWorkflow integrations

Using Reqio

Workflow integrations

Push new feedback, replies, status changes, and announcements from Reqio into Slack, Jira, or Linear as they happen.

Workflow integrations push feedback events out of Reqio into the tools your team already works in. Instead of checking the dashboard, a new bug report or a status change shows up as a Slack message, a Jira issue, or a Linear notification the moment it happens.

Where to find it

Integrations live at Project → Settings → Integrations. Only the project Owner can create, edit, or remove a connection, the same restriction as billing and MCP token issuance.

Each project can have one connection per provider: one Slack connection, one Jira connection, one Linear connection. Connecting a second time to the same provider replaces the existing connection.

Plan availability

SlackEvery plan
Available on Free, Pro, and Scale.
JiraPro and above
Attempting to connect on Free returns an upgrade prompt instead of a connection form. Pro +
LinearPro and above
Same gate as Jira. Pro +

Slack

  1. Create an incoming webhook

    In your Slack workspace, create an incoming webhook for the channel you want Reqio to post to (Slack → App settings → Incoming Webhooks → Add New Webhook).

  2. Copy the webhook URL

    Copy the webhook URL Slack generates.

  3. Connect in Reqio

    Go to Settings → Integrations → Connect Slack and paste the URL.

  4. Choose events

    Choose which events should post to the channel.

Every event delivered to Slack becomes a single message in the target channel.

Jira

  1. Start the connection

    In Reqio, go to Settings → Integrations → Connect Jira.

  2. Enter your site URL

    Enter your Jira site URL (e.g. https://yourteam.atlassian.net).

  3. Enter the account email

    Enter the account email for the Jira user Reqio should act as.

  4. Generate and paste an API token

    Generate an API token at id.atlassian.com → Security → API tokens and paste it in.

  5. Enter the project key

    Enter the project key (the short prefix on your Jira issues, e.g. ENG) where new issues should be created.

  6. Choose events

    Choose which events should create or update issues.

Linear

  1. Start the connection

    In Reqio, go to Settings → Integrations → Connect Linear.

  2. Generate a personal API key

    Generate a personal API key at Linear → Settings → API.

  3. Copy your team id

    Copy your team id from the team you want issues created in.

  4. Paste and choose events

    Paste both into the connection form, then choose which events should reach the team.

Events you can subscribe to

Each connection subscribes to one or more event kinds independently: a Slack connection can watch everything while your Jira connection only watches new feedback, for example.

New feedbackevent
A visitor submits a new public feature request.
Conversation replyevent
A visitor sends a message in a private conversation thread (Query, Bug, Unexpected behavior, or Feedback).
Status changedevent
A request moves to a new pipeline status (Needs action, In progress, Completed).
Announcement sentevent
Your team sends a project-wide Announce.
Pull request openedevent
The GitHub agent loop opens a pull request for a bug.
Agent needs contextevent
The GitHub agent loop has questions before it can start work on a bug.

You must select at least one event kind when you create a connection. Change the selection at any time from the connection's row in Settings → Integrations.

Delivery log and manual resend

Every delivery attempt, success or failure, is recorded in the delivery log at Settings → Integrations → Delivery log, most recent first. A failed delivery shows the error the provider returned.

One automatic retry

Reqio retries a failed delivery once automatically before logging it as failed. If it still failed, click Resend on that log entry to replay the exact same event. Resending creates a new log entry; it never edits the original.

Disconnecting

Click Disconnect on a connection to remove it. This immediately deletes the stored credentials; there is nothing to revoke on the provider side, since Reqio never stores more than it needs to deliver events. Past deliveries stay in the log; no new events are sent once a connection is disconnected.

Security

Connection credentials (the Slack webhook URL, the Jira API token, the Linear API key) are encrypted at rest. Reqio never displays a stored credential in full, only the trailing characters, so you can tell connections apart without the full secret being shown again.