Start with a practical job, tailor the instructions, and let OpenTag deliver each sourced result to a Slack channel or DM.
Slack Marketplace approvedBacked by
Three routines that show how scheduled work can span metrics, meetings, and engineering.
Compare signups, activation, churn, and revenue with the previous week, then explain the changes worth discussing.
PostHog
Stripe· Read onlySlack“Every Monday at 09:00 [timezone], compare last week's signups and activation in PostHog with subscription and revenue changes in Stripe. Post a sourced summary in #growth.”
Find pull requests waiting for review for more than a week and group them by likely blocker.
GitHub· Read onlySlack“Every weekday at 09:30 [timezone], list pull requests in the app repository that have waited for review for more than seven days. Group them by blocker and post links in #engineering.”
Receive a private brief with who you are meeting, your history, open commitments, and source links.
Google Calendar
Granola· Read onlySlack“Before my external meetings, send me a private Slack brief with the attendees, our history from Granola, open commitments, useful questions, and links to every source.”
Start with a real job, then change the source, timing, and output to fit your team.
18 routines
List open Attio deals, flag records with no next step, and link the ones that need attention.
AttioSlack“Every Monday at 09:00 [timezone], review open deals in Attio, flag any without a next step, and post a sourced summary with links in #sales.”
Find deals expected to close this month that have no recent activity or next step.
HubSpotSlack“Every weekday at 08:30 [timezone], find HubSpot deals due to close this month with no recent activity or next step. Post the owner, amount, and deal link in #sales.”
Prepare the people, company context, and open questions before a sales meeting.
Google Calendar
ApolloSlack“Before each sales meeting on my Google Calendar, research the company and attendees in Apollo and send me a private Slack brief with sources and open questions.”
Compare signups, activation, churn, and revenue with the previous week, then explain the changes worth discussing.
PostHogStripe· Read onlySlack“Every Monday at 09:00 [timezone], compare last week's signups and activation in PostHog with subscription and revenue changes in Stripe. Post a sourced summary in #growth.”
Summarise spend and results on Meta Ads using the same comparison window each week.
Meta AdsSlack“Every Friday at 15:00 [timezone], compare this week's Meta Ads spend and results with last week using the same attribution window. Post the largest changes in #marketing.”
Bring traffic and search performance into one weekly report with links to the source data.
Plausible
Search ConsoleSlack“Every Monday at 10:00 [timezone], compare last week's website traffic in Plausible and search performance in Google Search Console with the week before. Post the changes and source links in #marketing.”
Find pull requests waiting for review for more than a week and group them by likely blocker.
GitHub· Read onlySlack“Every weekday at 09:30 [timezone], list pull requests in the app repository that have waited for review for more than seven days. Group them by blocker and post links in #engineering.”
Group overdue and blocked Linear issues by owner so the team can clear the right work first.
LinearSlack“Every weekday at 09:00 [timezone], find overdue or blocked Linear issues in the current cycle, group them by owner, and post a rollup with links in #product.”
Collect incomplete launch work from Linear and ClickUp and call out anything without an owner.
Linear
ClickUpSlack“Every morning at 09:00 [timezone], check the launch projects in Linear and ClickUp. List blocked or incomplete work, missing owners, and the latest relevant comment in #launch.”
Receive a private brief with who you are meeting, your history, open commitments, and source links.
Google CalendarGranola· Read onlySlack“Before my external meetings, send me a private Slack brief with the attendees, our history from Granola, open commitments, useful questions, and links to every source.”
Summarise the day's invitees, booking details, and schedule gaps before the first call.
CalendlySlack“Every weekday at 08:00 [timezone], review today's Calendly bookings and send me a private Slack digest with invitees, booking details, and gaps between calls.”
Report what changed since the last briefing across the documents and conversations you can access.
Notion
Google DriveSlack“Every other Thursday at 15:00 [timezone], brief me on what changed in Project Atlas since the last report. Use Notion, Google Drive, and invited Slack channels, and link every source.”
List overdue invoices and show which customers account for the largest outstanding balance.
Stripe· Read onlySlack“Every Monday at 09:00 [timezone], list overdue Stripe invoices by age and show which customers account for the largest outstanding balance. Post the sourced report in #finance.”
Bring accounting records and the close checklist together, then flag missing inputs and owners.
Xero
Google SheetsSlack“At 09:00 [timezone] on the last three weekdays of each month, compare our Xero records with the close checklist in Google Sheets. Post missing inputs and their owners in #finance.”
Find agreements still waiting on signatures and group them by owner and time outstanding.
DocuSignSlack“Every Wednesday at 10:00 [timezone], list DocuSign envelopes still waiting on signatures, grouped by owner and time outstanding. Post links in #operations.”
Group unanswered pricing and support threads, then prepare reply drafts without sending them.
Gmail· Approval to sendSlack“Every weekday at 15:00 [timezone], find unanswered pricing and support threads in Gmail, group them by topic, and prepare reply drafts. Do not send them; post the draft links in my Slack DM.”
Group open HubSpot tickets by age and theme and call out requests without an owner.
HubSpotSlack“Every morning at 08:30 [timezone], group open HubSpot support tickets by age and theme, call out any without an owner, and post links to the oldest requests in #support.”
Batch new human messages from invited support channels and point out requests that still need a reply.
Slack“Every hour, batch the new messages from people in the invited support channels. Group them by theme and post any unanswered requests in #support-triage.”
Name what to read, the period to cover, the result you need, when it should run, and where it should go. Run it once and check the result before relying on the schedule.