Reference · built on requestOperator by FibricReporting & analysis

Action Follow-up

Tracks commitments recorded in review meetings against the work tracker and proposes reminders or reassignment when items go overdue.

Request accessPricing ↗

About

Every review meeting ends with commitments, and most of them are written somewhere the tracker never sees. Action Follow-up reads the review channel's history in Slack, where commitments are posted, and the tracker where work is meant to live: Jira issues found by JQL, Asana tasks by assignee and due_on, Linear issues by team. It matches each commitment to an item or notes that none exists.

When an item passes its due date, or a commitment has no item a set number of days after the meeting, it proposes the next step: a reminder to the owner, a due-date change, a reassignment, or a new task. Each step waits for a person to approve it. The operator leaves a record of what was promised, what was tracked, and what happened.

This is a reference listing. It documents what Fibric would read from Action Follow-up and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Messages in the review channel from Slack conversations.history, within the meeting window, where commitments are recorded
  • Issues assigned to the committing people, with status and due date, found through the Jira search endpoint with JQL
  • Tasks by assignee and workspace from the Asana tasks endpoint, with due_on, completed, and modified_since
  • Issues with assignee, due date, and state from Linear through the GraphQL API
  • Prior commitments and their outcomes, so a repeat commitment is shown against its history
  • Approve, edit, and dismiss responses on the reminders and reassignments it proposes

Proposed actions

  • Target capability: propose a reminder to the owner in Slack through chat.postMessage, quoting the commitment and the item's due date
  • Target capability: propose reassigning an overdue Jira issue through the assignee endpoint, to the person named in the meeting
  • Target capability: propose a new due_on or assignee on an Asana task through PUT /tasks/{task_gid}
  • Target capability: propose creating a task through POST /tasks in Asana or issueCreate in Linear for a commitment with no tracker item
  • Target capability: propose a follow-up line in the next review's channel listing what was promised and what closed

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Friday review, Tuesday reminder

    Commitments posted in the review channel on Friday are matched to Jira issues. On Tuesday one issue is past due with no update. The operator proposes a Slack reminder to its assignee quoting the commitment.

    With Slack, Jira

  • A promise with no task behind it

    A commitment in the channel has no Asana task three days after the meeting. Action Follow-up proposes creating one through POST /tasks with the owner, the due date said in the meeting, and a link to the message.

    With Slack, Asana

  • Reassign when the owner is out

    The assignee of an overdue Linear issue is on leave. The operator proposes an issueUpdate to the person the meeting named as backup, and a note in the channel.

    With Linear, Slack

Requirements

  • A Slack channel where review commitments are posted, with the app added as a member and the channels:history scope
  • A Jira project, Asana workspace, or Linear team where the committed work is tracked, readable by the connector
  • For reassignments, Assign Issues permission in the Jira project or tasks:write in Asana
  • A rule for what counts as a commitment in the channel, such as a message format or a reaction the team agrees on
Authentication
Action Follow-up holds no credentials. It reads the review channel through the Slack connector and trackers through the Jira, Asana, and Linear connectors you connect, and writes reminders and changes through the same connectors after approval.

Limits

  • A commitment it cannot parse is listed as unmatched for a person to resolve. It does not guess an owner.
  • Slack conversations.history reads only channels the app is a member of, and new apps are limited in how many messages a call returns.
  • Jira assignment through the assignee endpoint needs Assign Issues permission; without it the proposal cannot be carried out.
  • It reminds, reassigns, and creates tasks. It does not close items, change priorities, or message anyone outside the tracker's members.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Action Follow-up ↗

Questions and answers

What does a person approve?
Each reminder, reassignment, due-date change, and new task, shown with the commitment it came from, the tracker item it matched, and the person it will reach. You can approve, change the recipient or date, or dismiss with a reason.
What record does it leave?
Per meeting: the commitments read, the tracker item matched to each or the note that none existed, every proposal and its outcome, and the close date when the item was done. The next review sees the list in one place.
Does it message people on its own?
No. A reminder is a proposal until a person approves it. The operator reads channel history and trackers, and writes through Slack, Jira, Asana, and Linear only after approval, one action at a time.
Ask about Action Follow-up

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy