Run a recurring cross-app status update

This workflow sets Olyvr to gather a project’s status on a schedule and post the update for your team, without you asking each time.

Planned

Not available yet. Olyvr runs a workflow only when you ask in chat; it has no scheduler. What’s missing is a way to set a schedule, run it at the right time, and decide what happens when a run is missed or a slow run overlaps the next one. The steps below describe how it is intended to work.

Today you can run the same request yourself each morning. Olyvr reads the status document from Google Drive, reads the issues through the Jira plugin, and posts to Slack through the built-in Slack plugin after you approve.

What you need

• A Google account connected in Memory Data Sources, with access to the status document.
• The Jira plugin, signed in to the right site.
• The built-in Slack plugin, signed in to the workspace with the channel.
• A model.

Ask Olyvr

Every weekday at 9am Los Angeles time, summarize the Launch Status doc and the open issues in the LAUNCH Jira project, then post the update to #launch in the Acme workspace.

What Olyvr does

When this is available, Olyvr will:

1. Show the sources, the Slack workspace and channel, the time zone, how often it runs, and whether each post needs your approval.
2. Save the schedule once you confirm, and show when it runs next.
3. At each run, read the current document and issues and write a fresh summary.
4. Post one update per run. Unless you allow posting without asking, each post waits for your approval.
5. Let you pause, resume or turn off the schedule, and show the last result and any missing permissions.

Check the result

• One update in the channel for each scheduled weekday, with that day’s content.
• No repeated posts after Olyvr restarts.
• After you turn the schedule off, nothing more is posted.