Skip to content
Midpoint
Book a demo Hire your team

Automations

Hand over the job, not just today's task.

Describe the job in plain words, and the worker sets up the workflow and runs it on its own computer.

Hire your team Book a demo
Finn's Daily revenue report running in its workflow window: daily at 7:30 AM, seven named steps from Stripe and HubSpot to a Python script, Google Sheets and Gmail, each marked done as the run moves on, until it succeeds in 2m 51s.
Finn's Daily revenue report running: daily at 7:30 AM, and the first of its seven named steps, each marked done as the run moves on.

01 How it works

Set up by describing it, not by building it.

  • Jobs in plain words. Each one named for what it does, and hosted by one of your workers.
  • It starts on its own. A schedule, a webhook, an app event or Run now.
  • Status at a glance. Enabled, running or needing attention, for each worker's jobs.
The Automations page's list of workflows and scheduled tasks: twelve jobs across six workers, Finn, Iris, Scout, Luna, Poppy and Bobby, each named in plain words with the worker that hosts it, its schedule and its status. Among them the weekday blog post and the 7am brief at 7:00 AM, the nightly model training run at 1:00 AM, renewal reminders running now, every new sign-up qualified, started by a trigger, and SOC 2 evidence collection, which needs attention.
Seven of the twelve jobs on the Automations page, each named in plain words and hosted by a worker: Weekday blog post, 7am brief, Daily revenue report, Nightly model training run, Renewal reminders, Qualify every new sign-up, Month-end close checklist.

02 Steps

Steps that do whole pieces of work.

A single step can be a full session of browser work across many pages, a call to any connected app, or a script.

The whole workflow window of Finn's Daily revenue report: on, with Run now and the next run tomorrow at 7:30 AM; how it starts, daily at 7:30 AM; its seven steps, each with the app or script it uses; its last runs, one failed at step 3; and step 3, reconcile.py, open in the code editor, saved, with changes applying from the next run.
How the Daily revenue report starts, daily at 7:30 AM; its seven steps, each with the app, script or worker it uses (Stripe, HubSpot, reconcile.py, a check within $50, Finn writing the summary, Google Sheets, Gmail); and its last runs, one failed at step 3 when NetSuite rejected the ledger export.

03 When a run fails

Failures come to you.

The run stops at the step that failed and says why. Its worker writes to you, ready to fix the run, pause it or explain what went wrong.

Yesterday's 7:30 AM run, failed: what went wrong at step 3, NetSuite rejected the ledger export with 401 Unauthorized because the integration token was rotated on Nov 8, and nothing was written or sent. Steps 1 and 2 done, step 3 failed after 19s, steps 4 to 7 did not run.
Finn's message yesterday at 7:31 AM: the Daily revenue report stopped at step 3 because NetSuite no longer accepts Finn's connection, and nothing was written or sent. Reconnect NetSuite and Finn re-runs the report straight away. Under it, the NetSuite card: connected, and Finn resuming.
What went wrong at step 3, Reconcile with the NetSuite ledger: NetSuite rejected the ledger export, 401 Unauthorized; the integration token was rotated on Nov 8; reconcile.py stopped before reading any entries, and nothing was written or sent.
Finn's message yesterday at 7:31 AM: the Daily revenue report stopped at step 3 because NetSuite no longer accepts Finn's connection, and nothing was written or sent. Reconnect NetSuite and Finn re-runs the report straight away. Under it, the NetSuite card: connected, and Finn resuming.

04 Examples

Jobs a worker can take on.

Examples, not customer stories. We run the marked ones ourselves.

  • Linear issues to tickets

    A new issue in Linear. A Midpoint ticket on the right board, with a worker on it.

  • Answers in Slack

    A question in a Slack channel. Answered in its thread, with links to its sources.

  • Daily revenue report

    We run this one

    Daily. The revenue numbers, before anyone asks.

  • Carrier quotes

    A new submission by email. Quotes from each carrier's portal, side by side in one sheet.

  • Vendor invoice matching

    When an invoice arrives. Matched to its order, for approval.

  • Pull request review

    A pull request opens in GitHub. A review on the pull request, with what to test.

  • New sign-up research

    Each new sign-up. A researched profile, added to your CRM.

  • Shipment tracking

    Every 4 hours. Each open shipment checked on its carrier's site, with delays flagged.

  • First look at support tickets

    A new ticket in Zendesk. Tagged, routed, and answered in draft from your help center.

  • Weekday blog post

    We run this one

    Every weekday. A researched post, optimized for your keywords in Google Search Console, and published. Every week, a strategy for what to write next.

  • Contract first read

    A contract arrives by email. Read against your playbook, with the clauses to discuss.

  • Sign-up flow check

    Every hour. Your sign-up clicked through in a real browser, and any failure reported.

  • Requests from Slack

    A request posted in a Slack channel. A ticket on the right board, linked back in the thread.

  • Payout reconciliation

    Daily at 6:30 AM. The payouts that don't match the ledger.

  • Inbox triage

    A new email in Gmail. Sorted and labelled, with replies drafted for you to approve.

  • Policy renewals

    Weekdays at 8:00 AM. Policies due in 60 days, with each carrier's renewal terms from its portal.

  • Failed payments

    A payment fails in Stripe. The account checked, and a note to the customer drafted.

  • Renewal reminders

    Daily at 9:30 AM. Reminder drafts at 60, 30 and 7 days out.

  • New customer setup

    A new subscription in Stripe. The customer added to HubSpot, with an onboarding ticket for the team.

  • Customer checks

    We run this one

    Four times a day. The results, reported to the team.

  • Website leads

    A form sent from your site. The lead researched and added to HubSpot, with a reply drafted.

  • Freight quotes

    A quote request by email. Rates from each freight portal, with the best options drafted in reply.

  • Certificates of insurance

    A certificate request by email. Filled in from the policy, and sent once you approve.

  • Weekly search report

    We run this one

    Once a week. How the site does in search.

  • Document filing

    A file emailed to the worker. Renamed, filed in Google Drive, and logged in a sheet.

  • Prospect lists

    Mondays at 8:00 AM. Companies that fit your market, researched on the web and added to HubSpot.

  • Nightly model training

    Daily at 1:00 AM. A new model, held for your approval.

  • Interview scheduling

    A candidate replies with times. The interview put on the calendar, and the confirmation drafted.

  • Listing matches

    Daily at 7:00 AM. New listings that fit each buyer, from the listing sites, sent to their agent.

  • Order checks

    A new order in Shopify. Address and stock checked, and anything off flagged before it ships.

  • Weekly release notes

    Fridays at 2:00 PM. The week's changes, written up.

  • New applicants

    A new application. Read against the role, with a short note for the hiring manager.

  • Vendor statements

    On the 1st of each month. Each vendor portal's statement downloaded and matched to your payables.

  • Morning brief

    We run this one

    At 7am. Today's outside meetings, sent only to you.

  • Refund requests

    A refund request by email. The order looked up, and the refund prepared for your approval.

  • Permit status

    Weekdays at 10:00 AM. Each open permit checked on its city's portal, with changes logged.

  • Customer screening

    Each new customer. Checked against public sanctions lists, with any match held for review.

  • Competitor watch

    Mondays at 9:00 AM. Competitors' sites and pricing pages checked, with what changed.

  • Licence checks

    On the 1st of each month. Each clinician's licence checked on the state board's site, with expiries listed.

  • Product usage report

    We run this one

    Daily. How the product was used, for the team.

  • Supplier stock

    Weekdays at 7:00 AM. Stock from supplier portals, with reorders drafted for items running low.

  • Support digest

    Fridays at 4:00 PM. The week's tickets grouped by issue, with the top requests for the product team.

  • Order entry

    Each order by email. Entered in your ordering system through its website, then checked.

  • Payer policy updates

    Mondays at 8:00 AM. Changes to each payer's billing policies, from its site, summarized for billing.

  • Regulatory updates

    Mondays at 9:00 AM. New guidance from the regulators you follow, summarized for your team.

05 Controls

Jobs that run under your rules.

  1. An on/off switch and Run now on each workflow.

  2. Each job on its worker's own computer, with the apps you let it use.

  3. Email it sends checked against the recipients you allow.

  4. Usage by day, by worker and by person.

Hand over one job. Read its first run.

Hire your team Book a demo

Your first worker is free for two weeks. No card.