Workflows

Describe a job. Your agent does it.

Write what you want done in a sentence or two. LoopEngine plans each step, shows you where it will ask you, and sets it up. Nothing changes until you approve the plan.

Four steps

From a sentence to a job that runs itself

  1. 1

    Describe it

    Pick the agent that does this kind of work, then say what starts it, the steps, and where you want to decide, the way you'd brief a colleague.

    • “Every Monday, find timely blog ideas, ask me which to write, draft it, and let me review it before it goes up.”
    • No forms to fill in: a sentence or two is enough
  2. 2

    Check the plan

    LoopEngine reads what the agent already has, its identity, apps and messaging, and plans each step. Nothing is created until you say so.

    • Each step becomes a tool, a question to you, or an approval
    • It picks abilities for the tools: ones you have, or public ones to add
    • Its permissions, the keys it needs and its schedule, all shown before anything changes
    • A step nothing can do yet is marked Missing, so there are no surprises
    • If the job isn't the agent's kind of work, it says so and offers a new agent for it
  3. 3

    Add it to the agent

    Add any app or messaging the agent is missing, then create it. The workflow goes into that agent.

    • Missing apps and messaging are listed with links, and Create waits until they're in place
    • The agent keeps every rule it already has
    • Its schedule starts paused, and a checklist lists only what's left to set up
  4. 4

    Run it

    Run it once from the agent's page to see it work, then turn its schedule on.

    • Questions and approvals reach you in Slack, Lark or email
    • Each agent lists its workflows, with Run now and the schedule's state

An example plan

Every step, and where it stops for you

“Every Monday, find timely blog ideas, ask me which to write, draft it, and let me review it before it goes up.”

Runs every Monday at 09:00, paused until you turn it on. It needs one key, for Firecrawl.

StepBecomesCheckpoint
1Search the web for timely ideasfirecrawl_search
from the Firecrawl ability
Runs on its own
2Shortlist the three bestThinking it throughIts own work
3Ask which one to writeA question in SlackAsks you
4Draft the postWritingIts own work
5Publish it after reviewcreate_post
from your CMS's ability
You approve

Examples

Jobs teams hand off as workflows

Each is the message you'd type into New workflow: use it as it is or change it to fit, and approve the plan. The first seven are also ready-made in the console, with the plan already done.

Customer service

Answer customer emails

“Every 10 minutes, check our support inbox. For each customer email, look up their order in Shopify and our policies, and reply in the thread. Let me approve every reply, and leave refund requests for the team.”

GmailShopify

Asks you before: sending a reply

Customer service

Refund approvals

“Every 10 minutes, find refund and return requests in our inbox. Check each against the Shopify order and our return policy, work out the amount, and refund it. Ask me before any refund or reply goes out.”

GmailShopify

Asks you before: issuing a refund; sending the reply

Operations

Triage an incident

“When our alerting tool sends an alert, rate how bad it is, check GitHub for the deploys and merged changes that likely caused it, and send me a short summary in Slack. Ask me before opening or commenting on an issue.”

GitHubSlack

Asks you before: opening or commenting on issues

Finance

Check expense claims

“Every 15 minutes, read new claims in the claims inbox with their receipts, check each against our expense policy, and email the approver a one-line verdict. Never approve or pay anything yourself.”

Gmail

Asks you before: replying to the claimant

Sales

Lead follow-up

“Every hour, pick up new leads in HubSpot, research each company on the web, and send a short, personal first email. Ask me before sending, and before updating the lead.”

HubSpotFirecrawlGmail

Asks you before: sending the first email; updating the lead

Operations

Inbox to tasks

“Every 10 minutes, turn each request in our shared inbox into a GitHub issue with an owner and a due date, then tell the sender who is handling it. Let me approve the reply.”

GmailGitHub

Asks you before: replying to the sender

Describe the job once. Keep the final say every time.