Node catalog

A node is one step or surface in a Loop. Each node has typed input and output ports plus a small configuration form. The editor allows identical types, flexible Any ports, and a single item feeding a matching list port. It rejects other connections before saving.

Loops currently has 26 node kinds across six categories.

Triggers

Every runnable Loop needs at least one trigger.

Manual trigger starts when you choose Run in the editor.
Schedule starts an active Loop on a five-field UTC cron schedule. The dispatcher checks due schedules every five minutes.
Event starts an active Loop when a supported CRM event happens.

See Triggers for the event list and testing options.

Data

Data nodes gather or narrow rows without changing the CRM.

Lead search reads leads matching an optional status, tags, assignees, and result limit.
Lead match compares incoming properties with CRM lead preferences using budget and bedrooms or tags.
Lead from event reads the lead ID from an event payload and fetches that CRM lead. Put it between a lead event and an AI node that needs a lead record.
Resales Online search queries the connected Resales Online inventory by price, bedrooms, city, and limit.
Filter keeps input items that match its configured predicate.

AI

AI nodes run as durable model steps. Their tool access is scoped to the current organization and run. They produce proposal drafts or a structured refusal, never a direct CRM write.

Personalized email reads recent lead context and prepares one email proposal per input lead. Leads without an email address are skipped by the fan-out.
Re-engage stale lead reads recent context, can search connected properties, and prepares a re-engagement email. It can also propose a tag.
Qualify lead reads a lead and proposes a pipeline status, optional tags, and an optional CRM note.
Research agent searches scoped CRM leads and connected Resales Online property inventory, then prepares a short summary as a note proposal. Despite the current catalog label, it does not browse the general web or produce web citations.
Brochure generator takes properties and currently prepares a brochure outline as a note proposal. It does not render a brochure or PDF yet.

Connect AI output to Human approval if you want to review and execute the proposal. Without that downstream checkpoint, an AI draft is only run output.

Human

Human nodes suspend the durable run without keeping a browser open.

Human review presents the incoming rows as cards and waits for you to choose the subset that should continue.
Human approval persists each incoming AI draft as a proposal. Approving executes the matching email, status, tag, note, or task mutation. Dismissing leaves that row unchanged. The run resumes after every proposal has a decision.

Actions

Action nodes are direct CRM mutations. They execute when reached and are not automatically held for approval.

Send email sends incoming email drafts through the CRM email service.
Change lead status moves incoming leads to the configured status.
Create task creates a task for each incoming lead with a title and due-date offset.
Add tag adds the selected tags to incoming leads.
Create note adds the configured note to incoming leads.

Use direct actions only when immediate execution is intended. An AI node followed by Human approval does not need a second action node because approval executes the proposal itself.

Displays

Display nodes add useful live panels to the canvas. When connected, a display scopes itself to upstream data. When left unconnected, it can fall back to the corresponding organization-wide query.

Lead list shows filtered leads.
Power dialer shows a calling queue. Calls still come from the user's browser. The Loop does not dial by itself.
Deal board shows deals by stage.
Task list shows tasks by time bucket and assignee.
Email composer shows a draft for review or starts a blank composer.
Approval inbox shows proposals, optionally scoped to a specific approval node.

Display nodes are canvas surfaces. They do not change run data or the CRM by themselves.

Catalog limits

The catalog has no wait or delay node. There are also no general web-research or PDF-rendering nodes in the current runtime. If a node is not listed on this page, Fondaro AI cannot add it to a valid Loop.