Skip to main content

When an agent runs: a schedule, an event, a form or an Automation flow

Run an agent on a schedule, when something happens in CRM, CDP, your store or Email & Push, only when someone runs it — with a form — or from an Automation flow.

M
Monfri Team
Updated ·5 min read

An agent runs when you start it, on its schedule, when something happens, or when an Automation flow starts it. You set it in the agent's Settings → Triggers (or on the When card of the map). Every run reads as the agent's owner, with the owner's permission.

On a schedule

  1. Open the agent → Settings → Triggers.
  2. Under When it runs, choose On a schedule.
  3. In The schedule, pick Repeats — Every weekday, Every day, On chosen days, Every hour or Custom (cron) — the time and the Time zone. A new schedule starts in the workspace's time zone — the one in Monfri → Workspace settings; when none is set there, in your browser's. Any time zone can be chosen.
  4. Click Save as v….

Coming up on the Dashboard and Next run on the agent's page show when it runs next. A scheduled run reads as the owner only with the owner's permission; without it the run stops at its first read.

When something happens

  1. In When it runs, choose When something happens.
  2. Pick the Event:
    • CRM — a new lead (Only when: the lead has a company), CRM — a deal’s stage changed, CRM — a deal won or lost (the deal is won, the deal is lost), CRM — an invoice paid;
    • CDP — a profile enters a segment — with The segment: its id from CDP → Segments → the segment;
    • Store — a new order, Store — an abandoned cart — for a CloudCart store connected in Automation; the store is asked every few minutes;
    • Email & Push — a new web push subscriber — only the subscriber's number and device type reach the agent;
    • Newsroom — a new article published — news sites only: your own articles, usually minutes after they go up.
  3. Pick How it runs: Collect and run once an hour (the default — all the events of the hour in one run and one report), Once a day (at the time you set) or On each one.
  4. Set At most — 5, 20 or 50 runs a day. Its monthly budget stops it too.
  5. Save, then Activate (or save an active agent).

To start on an event, Agents makes a small flow Agent: … in Automation, as you, when you activate the agent. The flow is kept by Agents: it is changed only from the agent, and Automation refuses changes to it. Pausing or archiving the agent switches it off. Making or changing that flow needs a fresh Monfri sign-in — Agents asks for it.

Only when someone runs it

Choose Only when someone runs it. It runs with Run now on its page. In The form at “Run” you can add fields — Text, Long text, Number, Date or Choice — so that each run asks exactly what the agent needs. Without a form, a run takes an optional free text.

Some catalog agents — Content repurpose, Campaign drafter, Segment builder, Newsroom Copilot — work on your task each time, so they run only when you run them, never on a schedule.

From an Automation flow

  1. In Triggers → Also from Automation flows, add the flows that may start this agent. The list is read in Automation as you.
  2. In Automation, add the step Run agent to the flow and choose the agent: Steps in Monfri.

The flow gets only how the run ended, how many findings and proposals it has, and a link — never the report. A run from a flow reads as you, like a scheduled one. At most 20 runs an hour and 200 a day come from flows.

If something doesn't work

Sign in again: the flow in Automation that starts this agent is made as you, and that needs a fresh sign-in.

Click Sign in again, sign in to Monfri, and click Activate (or Save) once more.

Sign in again to see the flows: they are read in Automation as you, and that needs a fresh sign-in.

The list of flows needs a fresh sign-in. Click Sign in again.

This agent works on your task each time (a brief, a page or a question), so it runs only when you run it.

This agent cannot have a schedule. Run it with Run now and your task, or start it from an Automation flow.

Running it needs the owner's permission to read … as them

The agent reads a service and its owner has not allowed it yet. The owner clicks Allow reading … as me on its Overview or in Settings → Permissions.

An agent on a store event never runs

The store events work for a CloudCart store connected in Automation. Connect the store there first.

The event agent ran fewer times than events came

With Collect and run once an hour or Once a day, many events make one run. At most … runs a day and the agent's monthly budget also stop it.

Didn't find your answer?

Write to us and tell us what you were trying to do.