Your project tracker in Airtable is only as current as the last person who updated it. An Orkeste agent reads the issues in Jira or Linear for each project and updates the matching Airtable record: status, a short progress note and the risks to watch.
The problem
Project managers copy status from the delivery tools into the tracker by hand, once a week at best. Leadership reads a tracker that is two weeks behind.
How the workflow runs
Runs: Every day or every week.
Read the tracker: The agent reads the project records in your Airtable table.
Read the issues: For each project, it searches Jira (up to ten issues) or Linear (up to 20).
Work out the status: It writes the status, a progress note and the risks, using the rules in its briefing.
Approve: Record updates wait in Validations for the ops lead.
Update Airtable: Approved updates are written to the matching records.
With approval on for Airtable, records change only after the ops lead approves.
Who does what
Tracker updater: Keeps the Airtable tracker in line with delivery tools.
Ops lead (human): Approves the updates.
What this workflow does not do
Creates and updates records; it does not delete them or change fields and views.
Reads up to ten Jira or 20 Linear issues per search.