The repetitive work,
by department.

Trigger · Scheduler, 1st of the month 07:00.

1. Salesforce · Search Opportunities (Closed Won, this quarter), grouped by Owner.
2. Google Sheets · Read the "Quotas" tab for each rep's annual number.
3. Formula · attainment % = closed-won ÷ (quota × fraction of quarter elapsed); flag anyone below 70% of pace.
4. Google Sheets · Upsert one row per rep in "Comp Tracker": closed-won, quota, attainment %, flag.
5. Slack · @mention the manager of anyone below pace (added by Loopmint).

Trigger · HubSpot, New Form Submission.

1. Code by Zapier · enrich the contact (company, size) and apply the lead score.
2. Filter · continue only when the score clears the routing threshold.
3. Paths · pick an owner by territory rule; fall back to round-robin when none matches.
4. HubSpot · Create Task on the owner: "Follow up within 1 business day".
5. Slack · Send Channel Message to #inbound-leads: summary, score, source, @owner.

Role: SDR enablement engineer.
Input: every contact and call note from one Outreach dialing session.

For each contact, build this workflow:
1. Classify the disposition: Connected, No answer, Left voicemail, Not interested, or Meeting booked.
2. Write a one-line summary from the notes (objection raised, next step agreed, or reason for no answer).
3. Update the Salesforce record: disposition, last activity, and a logged call with the summary.
4. Create the next-step task with a due date: callback in 2 days for No answer, send a recap today for Meeting booked, nurture in 30 days for Not interested.
5. Flag any contact whose notes mention a competitor or a pricing objection for the AE (added by Loopmint).

Trigger · Schedule, every Monday 08:00.

1. Google Analytics 4 · Run a report: sessions, conversions, conversion rate (last 7 days vs prior 7).
2. Google Ads · Get metrics: spend, clicks, CPC by campaign.
3. HubSpot · Search new MQLs created last week.
4. Google Sheets · Add a row to "Weekly Marketing" with every metric.
5. Router + Filter · keep only metrics that moved more than 10% week over week.
6. Slack · Post the movers to #marketing, each with its delta and direction.

Trigger · Schedule, 1st of the month 06:00.

1. Search Console · Get search analytics: clicks, impressions, average position, top 20 queries (last month).
2. Google Analytics 4 · Run a report: organic sessions and conversions.
3. Google Sheets · Add rows to "SEO Monthly".
4. Array aggregator · compute month-over-month delta per metric and per top query.
5. Sort + slice · the five biggest gains and the five biggest drops.
6. Google Sheets · write a "Movers" block at the top of the sheet.

Trigger · HubSpot, a contact's score crosses the MQL threshold.

1. Salesforce · Upsert Lead (match on email); write the latest contact, company, and score.
2. Lookup · resolve the territory owner from the routing table; fall back to round-robin.
3. Salesforce · set Lead Owner and create a "Work this MQL today" task.
4. Slack · DM the assigned AE: lead name, score, source, HubSpot link.
5. On no match · route to #unassigned-leads so nothing goes silent (added by Loopmint).

Trigger · Zoom, webinar ended.

1. Zoom · Get the webinar participants and registrants.
2. HubSpot · Search or create a contact for each registrant.
3. Router · tag each contact Attended or No-show from the report.
4. HubSpot · Enroll Attended in "post-webinar nurture"; enroll No-show in "watch the recording".
5. Google Sheets · log the attendance rate and enrollments for the campaign record.

Trigger · new hire record { name, work email, role, department, start date }.

1. Google Workspace · Create the user; add the role's groups and aliases.
2. Slack · Invite the user; add the department's default channels.
3. Jira · Create the account; grant the role's project and permission scheme.
4. 1Password · Provision the role's vault and share credentials.
5. Gmail · Send the welcome and setup doc on the start date.
6. Audit · log every step with a timestamp; flag any failure for IT (added by Loopmint).

Trigger · HR marks an employee as departing { email, last day }.

1. Google Workspace · Suspend the account, reset the password, end active sessions.
2. SaaS connectors · Deactivate Slack, Jira, and every connected seat in order.
3. Google Drive · Transfer document ownership to the named manager.
4. Identity provider · Remove SSO and all group memberships.
5. Checklist · confirm each revocation; flag any that did not confirm for security (added by Loopmint).

Role: IT support automation engineer.
Input: a new ticket's subject, body, and requester.

Build this workflow:
1. Classify the category: access, hardware, software, how-to, or outage.
2. Set priority from the impact described: an outage or "can't work" is P1, a single-user blocker is P2, the rest P3.
3. Detect whether it matches a known issue or duplicates an open ticket.
4. Assign to the matching queue and apply the category and priority labels.
5. Draft a reply from the category's template, pre-filled with the requester's details, ready for an agent to review and send.
6. For anything classified as an outage, flag it for immediate human escalation (added by Loopmint).

Trigger · Schedule node, 1st of the month 06:00.

1. HTTP Request · pull active seats, plan, and last login per user from each admin console API.
2. Merge · combine every console into one list keyed by user email.
3. Function · flag every seat with no login in 30+ days; total the monthly spend it represents.
4. Google Sheets · write the full roster to "SaaS Spend" plus a "Reclaimable" summary block.
5. Slack · post the reclaimable total and seat count to #it-ops.

Trigger · Schedule, every day at 07:00.

1. HubSpot · Search deals updated in the last 24 hours (all properties).
2. Iterator · loop each deal.
3. Google Sheets · Search "Live Pipeline" by deal ID, then update or add the row.
4. Google Sheets · write the last-successful-sync timestamp to the header cell.
5. On error · post the failure to #ops-alerts so a silent gap never goes unnoticed.

Trigger · Scheduler, first business day of the quarter 07:00.

1. Connectors · pull each KPI from its source (revenue, pipeline, NRR, CAC, headcount) into "Board Metrics".
2. Formula · compute quarter-over-quarter change per metric.
3. Google Slides · update the linked figures and charts in the board deck.
4. Formula · flag any metric beyond its threshold and list it for narration.
5. Slack · notify #leadership that the deck is refreshed, with the flagged metrics.

Trigger · Schedule, every Monday 06:00.

1. Salesforce · Query accounts: name, plan, MRR, status.
2. Billing system · Get subscriptions: plan, MRR, status.
3. Array aggregator · match on account ID and diff each field.
4. Router · keep only the mismatches.
5. Slack · Post each mismatch to #ops with the Salesforce and billing values side by side.

Role: Program operations lead.
Input: this week's items from Jira, Asana, and Linear (closed, in-progress, blocked).

Build this workflow:
1. Pull items closed, in-progress, and blocked this week from all three tools.
2. Group by team and status, de-duplicating anything tracked in two tools.
3. Write a tight summary: what shipped, what's on track, what's at risk, and what's blocked and on whom.
4. Call out every blocked item older than five days as needing escalation (added by Loopmint).
5. Post to #weekly-status with a one-line headline per team above the detail.

Trigger · Schedule, 1st of the month 06:00.

1. QuickBooks / NetSuite · Get last month's general-ledger entries.
2. Bank feed · Get the month's transactions.
3. Array aggregator · match on amount, date, and reference.
4. Router · split unmatched entries from probable duplicates.
5. Google Sheets · write a "Close Exceptions" tab: each item, its amount, and why it was flagged for a human to clear.

Role: Accounts-receivable analyst.
Input: all open invoices with due dates, balances, and account contacts.

Build this workflow:
1. Bucket each invoice into Current, 1–30, 31–60, 61–90, or 90+ days overdue.
2. Total the outstanding balance per bucket and per account.
3. Draft a reminder email per overdue account, escalating tone by bucket (a gentle nudge at 1–30, firm at 61–90, a final notice at 90+), for a human to review and send.
4. Note any account both 90+ days overdue and above a material balance for a collections call (added by Loopmint).
5. Post a summary of total overdue by bucket to #finance.

Trigger · Schedule, 1st of the month 06:00.

1. Accounting system · Get this month's actuals grouped by GL category.
2. Google Sheets · Get the budget lines from the "Budget" tab.
3. Array aggregator · place each actual beside its budget line; compute variance ($ and %).
4. Filter · keep every category running more than 10% over budget.
5. Google Sheets · write the variances and refresh the "Budget vs Actuals" dashboard.

Trigger · CRM, a deal moves to Closed Won.

1. Invoicing tool · Create an invoice from the deal's line items, amount, and payment terms.
2. Approval · route the invoice to the owner for sign-off.
3. Invoicing tool · on approval, send it to the billing contact.
4. CRM · write the invoice number and status back to the deal.
5. On rejection · create a task for finance to review (added by Loopmint).

Trigger · ATS, a candidate's offer is marked accepted.

1. BambooHR · Create the employee from the offer: name, role, department, manager, start date, comp.
2. DocuSign · Send offer letter, tax forms, and policy acknowledgements as one envelope; track signatures.
3. Benefits portal · Open the enrollment window for the role's eligible plans and email the link.
4. Google Calendar · Book orientation, the manager 1:1, and the first-week check-in; invite the onboarding buddy.
5. Checklist · confirm each step; flag any unsigned document or missing election before the start date (added by Loopmint).

Role: Recruiting operations engineer.
Input: a new application's candidate details, resume text, and the job's scorecard.

Build this workflow:
1. Extract years of experience, key skills, and location from the resume.
2. Score against the role's must-haves only; write a two-line rationale and a recommend / review / decline call.
3. Apply the score and stage in Greenhouse; advance "recommend" candidates to the hiring manager with the rationale.
4. DM the hiring manager a digest of new "recommend" candidates and send every applicant a same-day acknowledgement.
5. Never score on protected characteristics; keep a human as the final decision-maker on every reject (added by Loopmint).

Trigger · Greenhouse, candidate moved to the panel stage.

1. Greenhouse · Read the panel: interviewers, the candidate, and stated availability.
2. Google Calendar · Get free/busy for every interviewer on the panel.
3. Logic · pick the earliest slots that fit the full panel plus the candidate's availability.
4. Google Calendar · Book each interview with the right interviewer; attach the scorecard and resume.
5. Gmail · Send the candidate the agenda and logistics; send each interviewer their prep packet.
6. Greenhouse · write the scheduled times back; alert the recruiter to anything that couldn't be booked.

Trigger · Schedule node, 1st of the month 06:00.

1. HTTP Request · pull active employees, new hires, and departures for the month from the HRIS API.
2. HTTP Request · pull PTO balances and approved upcoming time off per employee.
3. Function · headcount by department, net change vs last month, and any balance above the accrual cap.
4. Google Sheets · write the roster plus a Summary block to "Headcount & PTO".
5. Slack · post headcount, net change, and the balances-over-cap to #people-ops.

Trigger · NDA intake form submitted.

1. Document generation · Fill the approved NDA template: party names, effective date, term, mutual/one-way.
2. DocuSign · Send to the counterparty and internal signer; track status.
3. CLM / Google Drive · On full execution, save the signed PDF to the matter folder and log the register.
4. Review gate · if the intake requests any deviation from the standard template, hold for a lawyer's review before sending (added by Loopmint).

Role: Legal operations engineer.
Input: a new inbound contract's text, counterparty, and value/term metadata.

Build this workflow:
1. Identify the agreement type: NDA, MSA, DPA, order form, or amendment.
2. Compare key clauses (liability cap, indemnity, governing law, auto-renewal, termination) to the standard playbook; list each deviation with a low / medium / high risk tag and a one-line why.
3. Apply the type, risk level, and a "needs review" flag in the CLM; assign to the reviewer who owns that type and value band.
4. Post the reviewer a digest: type, counterparty, value, and the ranked deviations with links.
5. This is assistive triage only — never legal advice, never an approval; a qualified reviewer makes every call (added by Loopmint).

Trigger · Schedule, every Monday 07:00.

1. Google Sheets · Read the contract register: counterparty, type, value, end date, auto-renew, notice window, owner.
2. Logic · flag every contract whose notice deadline falls within 90 days; compute the last day to give notice.
3. Router · split auto-renewing contracts from fixed-term expirations.
4. Slack · post the 90-day list to #legal-ops and @mention each owner with the deadline and decision needed.
5. Google Calendar · create a reminder two weeks before each notice deadline.

Trigger · Schedule node, every Friday 16:00.

1. HTTP Request · pull open matters from the tracker: status, owner, stage, next deadline.
2. Google Sheets · read the obligations register: deliverable, contract, due date, owner.
3. Function · group matters by stage; surface every obligation or deadline due in 14 days and anything overdue.
4. Google Sheets · write the roster plus "Due soon" and "Overdue" blocks to the Legal Status sheet.
5. Slack · post open matters by stage and the due-soon / overdue items to #legal.

Trigger · Schedule, every Monday 06:00.

1. Analytics API · per-account usage: active users, key-feature adoption, last login.
2. Zendesk · open + recent ticket counts and escalations per account.
3. Salesforce · renewal date, ARR, and CSM owner per account.
4. Formula · health score from usage trend + support load + renewal proximity; tag green / yellow / red.
5. Google Sheets · write this week's snapshot to "Customer Health".
6. Slack · post every red or newly-downgraded account to #customer-success and @mention its CSM.

Role: Customer success operations engineer.
Input: a customer call transcript with participants, account, and call type.

Build this workflow:
1. Write a five-line recap, faithful to the transcript (no invented commitments or numbers).
2. List action items with an owner and due date.
3. Tag any churn-risk or expansion signal with the supporting quote.
4. Append the recap to the Salesforce timeline, create tasks, and set a risk/expansion flag.
5. Leave the note editable so the CSM confirms before it's shared (added by Loopmint).

Trigger · Scheduler, every day 07:00.

1. Salesforce · accounts renewing in the next 90 days, plus accounts whose usage crossed an expansion threshold.
2. Analytics · attach usage trend, seats-vs-licensed, and health score for each.
3. Salesforce · open a renewal task 90/60/30 days out, or an expansion opportunity when seats exceed the license; assign the CSM.
4. Slack · DM the CSM the play with context and a recommended next step; flag at-risk renewals for the manager (added by Loopmint).

Trigger · Schedule node, every weekday 08:00.

1. HTTP Request · onboarding accounts from the CS platform: start date, plan, CSM, milestone checklist.
2. HTTP Request · product events that mark each milestone (account created, data imported, first key action, team invited).
3. Function · mark each milestone done/pending; flag accounts stalled on a step past target.
4. Google Sheets · write progress and days-in-onboarding to the Onboarding Tracker.
5. Slack · DM the CSM every stalled account with the milestone and days stuck.

Role: Support automation engineer.
Input: a new ticket's subject, body, customer, plan, and recent history.

Build this workflow:
1. Categorize: billing, bug, how-to, outage, or cancellation.
2. Set priority from impact and plan; detect sentiment.
3. Draft a reply grounded in the matching help-center article or macro, with citations.
4. Apply category, priority, and tags; assign the queue; attach the draft as an internal note (never auto-send).
5. Post any outage, churn-risk, or angry-sentiment ticket to #support-escalations (added by Loopmint).

Trigger · Zendesk, ticket solved.

1. Delay · wait the configured time (e.g. 2 hours) so the resolution settles.
2. Email · send a one-click CSAT survey referencing the ticket and agent.
3. Router · on response, split detractors (low score) from passives and promoters.
4. Slack · post detractors to #support-escalations with score, comment, and ticket link.
5. Google Sheets · log score, agent, category, and comment to the CSAT sheet.

Trigger · Schedule node, every Monday 07:00.

1. HTTP Request · last week's tickets from Zendesk: volume, first-response time, resolution time, reopens, by channel and category.
2. Google Sheets · read last week's CSAT scores from the CSAT log.
3. Function · compute volume, median FRT, CSAT, backlog, top categories; flag any metric 10%+ worse than last week.
4. Google Sheets · append the week's row to "Support Metrics" and refresh the trend block.
5. Slack · post the headline metrics and any movers to #support.

Trigger · Scheduler, every day 09:00.

1. Zendesk · read the last 7 days of tickets with category, tags, and text.
2. Claude · cluster tickets describing the same underlying issue; count each cluster and note affected customers.
3. Jira · for any cluster over the threshold, create or update a linked issue with the count, examples, and affected ARR.
4. Slack · post the spike to #support-eng with the Jira link and tag the source tickets (added by Loopmint).