Workflows you could build with px0

the catalogue

Engineering: code and change

16 workflows

Repository chores: reviews, releases, CI, and the reports nobody writes by hand twice. github alone exposes 846 tools, so the digest shape generalises well past a Friday summary.

what you would type	reads	writes	cadence
Summarize the pull requests I reviewed this week and post it to #eng-standup	github	slack	Fri 17:00
List PRs open more than three days with no review and nudge each author in a DM	github	slack	daily 10:00
Draft release notes from the commits since the last tag and file them as a page	github	notion	on demand
Precheck my open PR against my Go review conventions and leave inline comments	github	github+ guideline	on demand
Report which merge queues stalled this week and what blocked them	github	slack	Mon 09:00
Turn last week's failed CI runs into a flaky-test list with counts, and file the top three	github	linear	Mon 09:30
Write this month's changelog page from merged PR titles, grouped by user-visible change	github	confluence	1st of month
Flag feature flags still on after 60 days, with the PR that introduced each	launch_darklygithub	slack	Wed weekly
List merge requests waiting on my group and rank them by how long they have waited	gitlab	slack	daily 09:00
Tell me what shipped to production yesterday, per service, with the deploy author	vercelgithub	slack	daily 08:30
Diff our Postman collection against the committed OpenAPI spec and open an issue per drift	postman	github	Thu weekly
Report strings added this week that have no translation yet, per locale	crowdin	jira	Fri 12:00
Summarize the review comments I received this month into what I keep getting wrong	github	file	monthly
Report which CI pipelines got slower this month and what step is eating the time	circleci	slack	Mon 10:00
Cross-check every merged PR this week against a linked ticket and list the orphans	githubjira	slack	Fri 16:00
When a PR touches a design-linked component, comment with the frame and who owns it	figmagithub	github	on demand

Developer productivity

18 workflows

One engineer's own day rather than reports about code. These assemble the context before you sit down, so the first twenty minutes go to work instead of to reconstructing where you left off.

what you would type	reads	writes	cadence
Restore my context: the branches, PRs, and tickets I touched yesterday, and what each was waiting on	githublinear	file	daily 08:00
Build one ranked queue for today from my assigned tickets, review requests, and mentions	githubjiraslack	file	daily 08:30
List what I am blocked on and who owns each unblock, so I can chase it in one message	githubjira	slack	daily 09:30
Triage my GitHub notifications into act now, read later, and ignore, with reasons	github	file	daily 09:00, 15:00
Draft the PR description from this branch's diff, following my PR conventions	github	github+ guideline	on demand
Write my standup update from my commits, reviews, and yesterday's messages	githubslack	slack+ guideline	daily 09:45
Tell me which of my branches are merged, stale, or duplicated, and which to delete	github	file	Fri 17:30
Report my review load: how many reviews I owe versus how many I am owed	github	slack	Mon, Thu 10:00
Batch this week's dependency PRs into one note: what upgraded, what looks risky, what to skip	github	github	Tue 11:00
Summarize test failures on my branches and separate mine from flaky infrastructure	github	file	daily 12:00
Turn this ticket into a design-doc skeleton, pulling in what I have already read on the topic	retrievejira	notion	on demand
Give me a tour of this repository: entry points, hot files, who last touched what	github	outline	on demand
Report where my coding hours actually went last week against what I planned	wakatimegooglecalendar	googlesheets	Fri 18:00
Find two focus blocks in next week’s calendar and hold them before anyone else does	googlecalendar	googlecalendar	Fri 16:00
Extract the recurring lessons from review comments I received this month	github	file	monthly
Assemble my brag doc entry for the quarter: what I shipped, reviewed, fixed, and unblocked	githubjira	googledocs+ guideline	quarterly
Collect every TODO and FIXME I added this month and turn the stale ones into tickets	github	linear	monthly
Write down what I learned today from the commits, comments, and docs I touched	githubslack	file+ guideline	daily 19:00

Engineering management

20 workflows

A manager's recurring work is assembly: the same facts out of four systems, shaped into a status, a one-on-one, or a decision. Automate the assembly and keep the judgement.

what you would type	reads	writes	cadence
Post a Monday sprint status: what is done, what slipped, and what nobody has started	jira	slack	Mon 09:00
Prepare my one-on-one pack for each report: their week's work, wins, blockers, and open threads	githubjira	file	daily 07:30
Write the weekly team report for leadership: shipped, at risk, incidents, and asks	jiragithubpagerduty	googledocs+ guideline	Thu 17:00
List cross-team dependencies we are waiting on and how long each has been waiting	jira	slack	Tue, Fri 10:00
Report the team's cycle time and review latency this sprint against the last three	githubjira	slack	sprint end
Flag work in progress that has stalled: assigned, untouched for a week, still open	linear	slack	Wed 10:00
Check next sprint's capacity against booked leave, holidays, and on-call rotation	bamboohrpagerdutyjira	slack	Thu before planning
Show how pages were distributed across the team last month and whether it was fair	pagerduty	googlesheets	monthly
Chase overdue action items from every postmortem, with the owner and the original incident	notionjira	slack	Mon 11:00
Report which epics slipped their target date this week and what moved them	jira	confluence	Fri 14:00
Age the tech-debt backlog and name the three items that keep causing incidents	githubsentry	notion	monthly
Audit our recurring meetings: attendee hours per week, and the three cheapest to cancel	googlecalendar	googlesheets	monthly
Summarize the retro into themes and open one issue per agreed action	dovetailmiro	linear	sprint end
Report interviewer load and which loops are short of a panel this week	greenhousegooglecalendar	slack	Mon 08:00
Track each new joiner at day seven, thirty, and sixty: first PR, first deploy, gaps	githubbamboohr	file	weekly
Assemble the evidence pack for each report's review from their own shipped work this half	githubjira	googledocs+ guideline	review cycle
Report seats and spend on our developer tools and what is unused	rampgithub	slack	monthly
Draft the project update our stakeholders keep asking for, from the tracker and the incident log	clickupsentry	notion+ guideline	Wed 16:00
Tell me who has not taken leave in three months, to me only, no channel	bamboohr	file	monthly
Name the reports I have not had a one-on-one with in two weeks and hold the slot	googlecalendar	googlecalendar	Mon 08:30

Incidents and reliability

11 workflows

pagerduty carries 363 tools and sentry 205, which covers the whole on-call paper trail: handover, triage, and the weekly review pack.

what you would type	reads	writes	cadence
Turn last night's error spike into a triaged bug ticket with the stack trace summarized	sentry	linear	daily 07:00
Write my on-call handover: what paged in the last twelve hours and what is still open	pagerdutysentry	slack	daily 09:00
Build the weekly incident review pack: pages, time to acknowledge, worst services	pagerduty	googledocs	Mon 08:00
Report error-budget burn per service and name the two closest to breach	datadog	slack	daily 08:00
Group this week's alerts by likely root cause instead of by alert name	new_relic	jira	Fri 16:00
Draft the post-incident timeline from the incident channel and the page log	slackpagerduty	notion	on demand
List every downtime window last week and the endpoint that caused it	better_stack	slack	Mon 07:30
Find the twenty loudest log lines this week and open one cleanup issue for the worst	datadog	github	Wed weekly
Cross-check open incidents against the change log and say which deploy likely caused each	servicenowgithub	slack	daily 10:00
Report alerts that fired more than ten times and nobody acted on, so we can delete them	grafana	slack	monthly
Check that every incident this month has an owner, an RCA, and a linked fix	pagerdutynotion	slack	monthly

Product and analytics

11 workflows

The dashboards already exist. What nobody writes weekly is the sentence explaining what moved, which is the shape a guideline improves most.

what you would type	reads	writes	cadence
Report the funnel's three biggest drop-offs this week against last, and what changed near them	posthog	slack	Mon 09:00
Fourteen days after launch, tell me who adopted the new feature and who bounced off it	amplitude	notion	on demand
Append yesterday's core numbers to the metrics sheet and flag anything outside two sigma	googlebigquery	googlesheets	daily 06:00
Turn our Metabase weekly questions into a written readout, not a screenshot	metabase	slack	Mon 08:30
Say which running experiments crossed significance and which should be stopped	posthog	linear	Tue weekly
List search queries that returned nothing this week, ranked by volume	algolia	jira	Fri 11:00
Summarize rage-click and dead-click hotspots by page	posthog	slack	Wed weekly
Flag traffic anomalies against the four-week baseline, by channel and landing page	google_analytics	slack	daily 07:30
Compile the quarterly board metrics narrative from the warehouse and last quarter's doc	databricks	googledocs	quarterly
Tell me which cohort retained best last month and what they did in week one	mixpanel	notion	monthly
Post the one number that moved most yesterday and the likeliest reason	posthoggithub	slack	daily 09:00

Customer support and customer voice

10 workflows

zendesk is one of the deepest toolkits in the catalogue at 452 tools. The useful automations convert ticket volume into engineering intent: themes, not counts.

what you would type	reads	writes	cadence
Group this week's support tickets by theme and open issues for the top three	zendesk	linear	Fri 15:00
List first-response SLA breaches by queue and who owns each	freshdesk	slack	daily 09:30
Turn repeated how-do-I questions into a docs backlog, one page stub each	intercom	notion	Mon weekly
Cluster this month's survey verbatims by cause and quote the sharpest three	delighted	slack	monthly
Flag open tickets from enterprise accounts and attach the account's renewal date	zendesksalesforce	slack	daily 08:00
Find feature requests mentioned by three or more customers this month	canny	linear	monthly
Write the customer-facing note for what we fixed that customers actually asked for	zendeskgithub	notion	Thu weekly
Summarize what the shop's angry reviews and tickets agree on	gorgiasshopify	slack	Fri weekly
Draft a reply for every ticket waiting on us, saved as a draft, never sent	help_scout	help_scout+ guideline	daily 09:00
Match this week's churned accounts to the tickets they filed first	intercomhubspot	slack	Mon 10:00

Sales, CRM, and revenue

10 workflows

Pipeline hygiene and call preparation, assembled from the CRM plus whatever else touched the account.

what you would type	reads	writes	cadence
Report which deals changed stage this week and which slipped out of the quarter	hubspot	slack	Mon 08:00
Nudge owners about deals with no activity in fourteen days, one DM per owner	pipedrive	slack	Tue 09:00
Before each call today, brief me on the account: history, open tickets, last emails	salesforcezendeskgmail	gmail	daily 07:00
Write the won-and-lost review with the reason each deal actually turned	hubspot	googledocs	Fri 16:00
Enrich this week's inbound signups and drop the ones with no company match	hunterpeopledatalabs	hubspot	daily 11:00
Pull yesterday's call recordings into CRM notes and next steps	gongfireflies	salesforce	daily 20:00
List contracts sent but unsigned for more than five days, with who to chase	docusign	slack	daily 10:00
Draft the follow-up email for every meeting I had yesterday, in my voice	googlecalendargong	gmail+ guideline	daily 08:00
Find accounts that went quiet for thirty days and rank them by what they are worth	attio	slack	Mon 09:00
Check the CRM against reality: deals with no contact, no amount, or no close date	salesforce	googlesheets	Fri 15:00

Finance and billing

9 workflows

stripe alone carries 415 tools, so coverage is rarely the constraint. These are the workflows whose write tool deserves the most scrutiny before you authorize it.

what you would type	reads	writes	cadence
Log this week's revenue and refunds into the finance sheet	stripe	googlesheets	Fri 18:00
List failed payments worth retrying and draft the recovery email for each	stripe	gmail	daily 09:00
Write the monthly recurring-revenue movement: new, expansion, contraction, churn	stripemaxio	notion	1st of month
Report invoice aging and who to chase, oldest first	quickbooks	slack	Mon 09:00
Flag card spend outside each team's monthly budget, with the merchant	rampbrex	slack	weekly
Reconcile yesterday's settlements against our ledger and report only the gaps	razorpay	googlesheets	daily 07:00
Summarize the accounts closing this month and which have unsigned paperwork	xerodocusign	slack	monthly
Report software renewals due in the next sixty days and last month's actual usage	rampstripe	slack	monthly
Assemble the quarterly tax pack from invoices and receipts, and list what is missing	xerogmail	googledrive	quarterly

Operations, people, hiring

9 workflows

Recruiting loops, leave, timesheets, and vendor paperwork: high-friction, low-judgement, and almost entirely assembly.

what you would type	reads	writes	cadence
Name candidates stuck in a stage for more than five days and whose action it is	greenhouse	slack	daily 09:00
Report the hiring funnel by role with pass-through rates per stage	lever	googlesheets	Mon weekly
Assemble the day-one pack for each new joiner: accounts, docs, first-week meetings	bamboohr	notiongooglecalendar	daily 06:00
Check next sprint's dates against booked time off and flag the collisions	bamboohrjira	slack	Thu weekly
Chase whoever has not logged hours, one DM each, no channel shaming	clockify	slack	Fri 17:00
List vendor contracts expiring in the next forty-five days and their owner	docusign	slack	Mon weekly
Summarize this week's interview scorecards into a hiring-committee brief	ashby	googledocs	Thu 18:00
Book each interview panel from who is genuinely free and send every interviewer the resume	ashbygooglecalendar	googlecalendargmail	daily 07:00
List offers sent but unsigned, how long each has waited, and who owns the chase	docusigngreenhouse	slack	daily 10:00

Marketing and content

10 workflows

Campaign reporting, competitor watching, and turning one published piece into the versions each platform wants.

what you would type	reads	writes	cadence
Draft next week’s content calendar from the backlog, in the voice I write in	notion	notion+ guideline	Fri 14:00
Turn the post I published into five platform-specific versions, queued not sent	firecrawl	typefullybuffer	on demand
Report campaign performance: opens, clicks, unsubscribes, and the subject that won	mailchimpklaviyo	slack	Tue weekly
List keywords that dropped more than three positions this week	dataforseo	googlesheets	Mon 07:00
Watch our competitors' pricing pages and report only what actually changed	firecrawl	slack	daily 08:00
Split webinar registrants into attendees and no-shows and draft each follow-up	zoom	mailchimp	on demand
Summarize what people said about us on Reddit and Hacker News this week	redditexa	slack	Fri 12:00
Report which paid campaigns are burning budget below target conversion	metaads	slack	daily 09:00
List pages that lost impressions this week despite ranking in the same position	google_search_console	googlesheets	Mon 08:00
Report which of my posts drove signups rather than likes	linkedinposthog	slack	Mon 09:00

Personal operations

10 workflows

The smallest workflows, and day to day the ones you notice most. They also need the fewest connectors to cover nearly all of this section.

what you would type	reads	writes	cadence
Brief me on today’s meetings and the emails I have not replied to	googlecalendargmail	file	daily 07:00
At the end of the day, list everything I said I would do in Slack today	slack	todoist	daily 18:30
Show inbox debt: threads waiting on me for more than three days, oldest first	gmail	slack	daily 16:00
Audit last week’s calendar: meeting hours, focus hours, and the worst offender	googlecalendar	googlesheets	Mon 08:00
For each meeting tomorrow, attach the last three emails with those people	googlecalendargmail	file	daily 19:00
Pull receipts out of my mail this week and add a row per expense	gmail	googlesheets	Sun 20:00
Assemble the travel pack for tomorrow's trip: flights, hotel, times, documents	gmailgooglecalendar	file	daily 20:00
Draft the replies I owe, in my voice, saved as drafts so nothing sends without me	gmail	gmail+ guideline	daily 17:00
Split this trip's expenses from the receipts and tell each person what they owe	gmail	splitwise	on demand
Tell me what I said yes to this week and what it cost me in hours	googlecalendarslack	file	Sun 19:00

Everyday life, no code involved

12 workflows

None of this is work. The people who need it most have never written a script, so the whole interface is one sentence and a time of day: the bills, the birthdays, the school mail, the weekend photos.

what you would type	reads	writes	cadence
Every Sunday, plan the week: everyone's events, who drives, and what clashes	googlecalendar	whatsapp	Sun 18:00
Remind me a week before every birthday and anniversary, with what I gave last year	googlecalendargmail	whatsapp	daily 08:00
List the bills due in the next ten days and how much each one is	gmail	todoist	Mon 07:00
Track every subscription quietly charging my card and flag the ones I stopped using	gmail	googlesheets	monthly
Summarize the school and society mail into what actually needs me to do something	gmail	whatsapp	daily 18:00
Turn everything I said I needed this week into one shopping list, sorted by aisle	whatsapp	todoist	Sat 09:00
Before I travel, tell me the weather where I am going and what that means for packing	weathermapgooglecalendar	whatsapp	daily 20:00
Split this month's shared household spend and tell everyone what they owe	gmail	splitwise	monthly
Make one album from last weekend's photos and share it with whoever was there	googlephotosgooglecalendar	googlephotos	Mon 09:00
Log this week’s runs against my goal and tell me plainly whether I am behind	strava	googlesheets	Sun 20:00
Find an evening next week that works for these four people and send the invite	googlecalendarcalendly	googlecalendar	on demand
Tell me what my savings and holdings did this week in one sentence, no charts	coinbasealpha_vantage	gmail	Fri 18:00

Brain-grounded workflows

8 workflows

These need no connector. inputs: retrieve and a guideline are the whole apparatus, so they run offline and cost nothing to authorize. Start here.

what you would type	reads	writes	cadence
Digest what I saved this week and name the thread running through it	retrieve	file	Sun 18:00
Review this design doc against the notes I have kept on distributed systems	retrievegithub	github	on demand
Draft a blog post from the three papers I read on backpressure, citing each	retrieve	file+ guideline	on demand
Build an interview question sheet from my saved system-design notes	retrieve	file	on demand
Tell me what I have read that contradicts the claim in this PR description	retrievegithub	file	on demand
Answer support questions in my words, using only what my brain actually says	retrievezendesk	zendesk	on demand
Tell me what I already decided about this, before I decide it again	retrieve	file	on demand
Turn my scattered notes on this topic into one page that does not contradict itself	retrieve	file+ guideline	on demand

pick one

Every workflow is one command away

Type the sentence, review the tools px0 resolved, and check it before it touches anything real.

terminal

› px0 workflows new
answer in your own words; press Enter on a blank line to stop
› What do you want px0 to do for you?
everyday at 9pm summarize all the commits I made and PRs I reviewed and post it to #eng-standup

› px0 workflows run friday-pr-digest --dry-run