Steps in Monfri: e-mail and push, CRM, CDP, Pages and agents

Steps for Monfri's own services need no setup: their connections are made for your workspace. They act for the workspace as a whole — a flow sees every CRM record, not only those of the person who built it.

E-mail and web push — through Push

Send e-mail from a flow with Push → Send email. It goes through Push from one of your workspace's confirmed senders — your own domain, or the Monfri address every workspace gets (hello@t….monfrimail.com) — never from a Monfri mailbox. It counts in your plan and appears in Push → Email → Transactional with the source Automation and the flow that sent it: Transactional e-mail.

• Type — required. Transactional for an order, an account, a reply to the person or a notice to your own team. Marketing for offers, news and promotions: Push sends it only to people who gave marketing consent, never to anyone who unsubscribed, and adds the unsubscribe link and your postal address.
• To and Subject are required. To takes up to 10 addresses separated by commas, and each person gets their own e-mail; anything that is not an address is left out and named in the result. To Name is for a single recipient.
• Email Template — one of your Push templates; its text and design are used. Without one, HTML Body is sent, or Text Body alone as a plain e-mail. Merge Data fills the template's {{tags}}: Merge tags.
• From — a menu of your confirmed senders; empty means the default sender. Add senders in Push → Email → Senders: Senders.
• Reply-To — where replies go; empty means the sender's own Reply-To.
• Frequency cap (hours) — skip the e-mail if this person already got one under the same cap within those hours.
• Recipe consent setting — recipes fill it from Marketing consent for recipe emails in the workspace settings. Leave it empty in your own flows.

Above the fields, the step says from which address your e-mails go — or why they cannot go yet: no confirmed sender, nobody with Can send campaigns in Push, a read-only workspace. Publish says the same, and publishes anyway; the e-mails go once it is fixed.

To send through your own mail server instead, use Your own mail server (SMTP) in the Advanced group: Connectors.

Some e-mails are not sent, and that is not a failure: the step is skipped and says why — the person unsubscribed or gave no marketing consent, the frequency cap, a blocked address, or a domain that does not exist (gmail.con). During the trial, a workspace sends up to 200 e-mails a day; past that, the run waits for the next day. When Push asks to slow down, it waits until Push allows it again — up to an hour. Both resume by themselves.

A web push goes with Send Notification — to one subscriber or several (Subscriber IDs, for example a CDP profile's push subscribers) — or Send to Segment, to a Push segment: Web push. Push sends no SMS; for SMS, see Connectors.

CRM

The step library lists the common ones: Create contact, Update contact, Find contacts, Create company, Create deal, Move deal stage, Close deal, Create lead, Qualify lead, Disqualify lead, Create task, Complete task, Create activity, Enroll in sequence, Add sequence step, Activate sequence, Create project, Create board, Move task to column, Create invoice, Mark invoice paid, Add note. A CRM step's Action list has the rest — get, list, update and delete of every record, tags, products, pipelines, payments, Create Invoice from Deal, Search CRM.

The rules of CRM hold in a flow too:

• Close Deal as lost, and Move Deal Stage into the lost stage, need a lost reason from your list.
• Disqualify Lead needs a reason: not_a_fit, no_budget, wrong_contact, timing, no_response, competitor, spam, duplicate, or one of your own.
• Qualify Lead creates the deal for the person behind the lead.
• Create Task needs a Project — every CRM task belongs to one. A follow-up call or meeting on a contact, deal or lead is Create activity.
• Enroll Contact in Sequence works only for an active sequence.

CDP

Track event, Identify user, Get profile, Update traits and List segment members — plus Get Cart Snapshot, Get Order Status and Get Consent in the step's Action list. A flow started by a CDP event or a segment usually begins with Get profile, to have the person's e-mail address and traits: Profiles.

Pages

In the Pages & Agents group, Monfri Pages: Create Page (in a space, with a title and Markdown text), Get Page, Search Pages, Create Database Row and List Database Rows.

Run agent

Monfri Agents → Run agent starts one of your agents and waits for it to finish — up to 15 minutes. It appears where your workspace has Agents.

• Agent — the agent's owner must allow the flow first, in Agents → the agent → When → Automation flows; until then the step fails with that reason.
• Task — what the agent should work on this time, with {{trigger.…}} values. It goes to the AI model as the agent's task, so pass only what it needs.
• Inputs — for an agent with a form, its fields.

The next steps get how the run ended — status, succeeded, the number of findings and proposals, proposals_waiting — and run_url, a link only the agent's owner can open; never the report itself. While it waits, the flow's run shows Waiting for the agent. It cannot be inside a loop, and Test Step does not start the agent.

If something doesn't work

This workspace has no confirmed default sender — add or confirm one in Push → Email → Senders.

Every workspace gets a sender on a Monfri address; confirm it, or make another confirmed sender the default: Senders.

… is not one of this workspace's senders. / The sender … is not confirmed yet.

From names an address that is not a confirmed sender of the workspace. Pick one from the menu, or click the link in the sender's confirmation e-mail.

Sending domain is not verified — re-check DNS records.

The sender's domain lost its DNS records: Send e-mail from your own domain.

Nobody in this workspace has the "Can send campaigns" permission in Push…

Automatic e-mails need at least one person who may send. A workspace admin gives it in Monfri → Members: Service access.

The Monfri trial has ended — sending is paused until a plan is active.

The workspace is read-only, so nothing is sent; the connection stays as it is. Activate a plan: Plans, the trial and read-only.

Pick why the deal was lost.

CRM needs a lost reason: add it to Close Deal or Move Deal Stage — the id or the key of one of the reasons set in CRM.

The project id field is required.

Create Task needs a project. For a follow-up on a person or a deal, use Create activity.