Idiligo

Run scripted online meetings through Idiligo, creating meetings from a script, connecting participants, and reading back prefilled content. Agents make sure every customer meeting covers the same required ground.

1 trigger 18 actions API key available

Idiligo website ↗ Platform Documentation ↗ Capability data verified 2026-08-03

On New Meeting Event reports the script reached its closing node

Agent reads the collected answers with Get Meeting Values

Agent confirms every field the script should have collected carries a value

Agent files the signed document from Get Meeting Attachments and writes the answers to the CRM

Agent compares the collected field set against the disclosures this script must cover

Agent posts the recap and any empty required field to the advice team channel

Compliance owner decides whether a meeting that skipped a required field has to be re-run

What This Integration Enables

Idiligo is the one service in this category that is not a scheduler and not a video tool. It is a script that happens to run as a meeting. A meeting is created from a traject code, and that code decides which nodes appear, in what order, and which named values get collected along the way. The person presenting cannot skip ahead past the disclosure, cannot improvise the order, and cannot finish without the fields the script asks for. That makes Idiligo a fit wherever the content of a customer conversation is the thing being governed: regulated advice, insurance and mortgage sales, clinical or benefits onboarding, any meeting a regulator or an auditor may later ask about.

For a FlowRunner agent this shape is unusually useful, because the meeting is addressable from both directions. Before the meeting, an agent calls Set Meeting Values to prefill the script with everything already known about the customer, so the presenter is not reading a policy number back over a call. During and after it, Get Meeting Values returns the collected answers as name and value pairs and Get Meeting Events returns the sequence of what occurred, which means the outcome of a meeting is structured data rather than a note somebody has to transcribe. Documents move the same way: Add Document From URL uploads a proposal against a named Upload node, and Get Meeting Attachments returns the uploaded, generated and signed versions afterwards. The agent handles all of that. The judgment about whether the script itself still says the right things stays with a person, which is exactly where FlowRunner's human-in-the-loop design puts it.

Without FlowRunner

Every meeting runs differently What gets covered depends on who took the call and how the day was going

Answers live in notes The client's responses are typed up afterwards, from memory, if at all

No record of what was covered Proving a disclosure was made means finding the person who made it

With FlowRunner

One script, every meeting The same nodes run in the same order regardless of who is presenting

Answers arrive as fields Get Meeting Values returns named pairs a flow writes straight into the CRM

An event log per meeting Get Meeting Events records what actually happened in the room, meeting by meeting

Use Case Scenarios

A regulated advice meeting that starts already filled in

An adviser's calendar shows a suitability review. The agent picks the case up from HubSpot, calls Create Contact for the client, runs Create Meeting against the approved traject code for suitability reviews, and pushes the client's holdings, risk profile and prior recommendations in with Set Meeting Values. It then calls Get Organizer URL for the adviser and Get Public Meeting ID to build the client's join link, and sends both with Send Meeting Email using the firm's approved mail template. The adviser opens a meeting where the facts are already on screen and the required sections are already queued, so the conversation is about the advice rather than about reading data aloud.

Onboarding where the paperwork comes back signed

A new client is onboarded through a scripted session. The agent uploads the engagement letter with Add Document From URL against the Upload node the script expects, then Attach Document To Meeting so it appears at the right step. When the session ends, Get Meeting Documents reports the sign URL and sign status per document, and Get Meeting Attachments returns temporary download URLs for the uploaded, generated and signed files. The agent pulls each file down promptly, because Idiligo stores them temporarily and the URL changes over time, and files them to the client folder in Google Drive with the meeting reference attached. Nobody chases a signature that was already collected.

The meeting that finished with a hole in it

On New Meeting Event fires as a session progresses. When the closing node is reached, the agent calls Get Meeting Values and compares the returned names against the set this script is supposed to produce. Most meetings match and the agent writes the answers back to the CRM, updates the case status and stops. When a required field comes back empty, the agent does not quietly write a partial record. It posts the meeting reference, the missing field and the relevant slice of Get Meeting Events into the advice team channel in Slack and holds the CRM write. Those are automation exceptions, and there are usually very few of them, which is the point: the reviewer reads the three meetings that went sideways instead of sampling all ninety.

Human-in-Loop Highlight

The gate on Idiligo is not on any single write. It is on the script. Create Meeting takes a traject code and nothing else about the content, so the agent has no visibility into what that script currently asks or what it currently discloses. Scripts get edited in Idiligo by whoever owns the sales or advice process, and a node removed on a Tuesday afternoon changes what every meeting covers from Tuesday afternoon onward. A meeting that was held without a required disclosure cannot be un-held. That is the irreversibility here, and it is a quiet one, because every API call succeeds exactly as before.

So the agent watches for the symptom rather than trusting the code. Before it starts a run of meetings on a traject code it has not seen recently, and every time Get Meeting Values on a completed meeting returns a field set that no longer contains a name the previous meetings on that script all produced, it stops and asks the compliance owner in their channel: "Script SUIT-04 collected 11 named values last week and 9 today. The fields consent_confirmed and risk_disclosure_read are no longer coming back. Was the script changed deliberately? I am holding the 6 suitability meetings queued against this code until you answer." Then it waits. The alternative is a batch of technically successful meetings that are individually unusable, and the person who owns the disclosure finding out from an auditor rather than from a digital andon cord.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

18 actions

Contacts

Create Contact Creates a participant contact from an email address, first name and last name, and returns the contact ID. This is the first call in almost every Idiligo flow, because a participant has to exist as a contact before it can be connected to a meeting.

Meetings

Create Meeting Creates a new online meeting based on a script, identified by its traject code. Returns the non-public meeting ID (callId) that every other meeting operation needs. The traject code is the decision that determines what the meeting will cover.
Connect Contact To Meeting Connects a participant contact to an online meeting using the non-public meeting ID and the contact ID. Used to attach the customer, and any additional attendee, to a meeting the agent just created.
Get Organizer URL Generates the URL the meeting organizer uses to enter the online meeting, with an optional return URL for where they land after it ends. Used to hand an adviser or account manager a one-click entry into a session the agent prepared.
Get Public Meeting ID Generates the public ID for a meeting and builds the participant join URL. The public ID is also what Set Meeting Value, Set Meeting Values and Get Meeting Events all require, so most flows call this immediately after Create Meeting.
Get Meeting Details Retrieves a meeting's details including its public ID, account number, event count, organizer username, language, comment and participant email. Used to reconcile a meeting record against a CRM case.
End Meeting Ends an online meeting, with an optional return URL. Used to close out a session programmatically when a downstream condition is met rather than leaving it open.

Meeting Data

Set Meeting Value Writes a single named value into a meeting, prefilling the matching field of the script. Used for targeted updates, such as dropping in a quote figure that was only calculated after the meeting was created.
Set Meeting Values Writes multiple named values into a meeting in one request, taking field names and values from the keys and values of the supplied object. This is the prefill step: everything already known about the customer goes in here so nobody reads it aloud from another screen.
Get Meeting Values Reads back all named values collected in a meeting as name and value pairs. This is how a scripted conversation becomes structured data, and it is also the signal a flow inspects when checking that a required field was actually collected.
Get Meeting Events Retrieves the events of a meeting that occurred after a given event count, each with an ID, a type and a value. Used to reconstruct what happened in the room, in order, when a meeting needs reviewing.

Documents

Add Document From URL Uploads a document to Idiligo from a publicly reachable URL, against the external ID of the matching Upload node in the script. Returns the document ID. Used to put a proposal, quote or contract in front of the customer at the step the script expects it.
Attach Document To Meeting Connects a previously uploaded document to a meeting. The script must contain an Upload node with the identical external ID, so document handling and script design have to agree with each other.
Get Meeting Documents Lists a meeting's documents with document ID, description, download URL, preview URL, size, date, sign URL and sign status. Used to check whether a document the customer was asked to sign has actually been signed.
Get Meeting Attachments Retrieves the uploaded, generated and signed documents of a meeting. Each entry carries a temporary download URL, because Idiligo stores the documents temporarily and the URL varies over time, so a flow should pull the file rather than store the link.
Get Document Status Retrieves the status of a document by its document ID. Used as a lightweight check in a follow-up flow that is waiting on a signature before it advances a case.
Delete Document Deletes a document by its document ID and reports whether the deletion succeeded. Used for cleanup after a document has been filed elsewhere, and worth treating carefully, because the copy in Idiligo is temporary to begin with.

Email

Send Meeting Email Sends an email for a meeting using a mail template configured in the Idiligo account, taking the recipient address, the template code and an optional attachments parameter. Used for invitations and for the follow-up that goes out once the meeting has produced its documents, so the wording stays the wording that was approved.

Triggers

1 triggers

Event Triggers

On New Meeting Event Fires for each new event in a watched meeting, polling the GetEvents operation and passing the number of events already processed. The first run records a baseline and emits nothing, and afterwards each unseen event fires once, de-duplicated by event ID, optionally restricted to a single event type. Used to react while the meeting is still running, or to catch the closing node and start the post-meeting flow the moment the conversation ends rather than whenever someone remembers to check.

Frequently Asked Questions

What can FlowRunner do with Idiligo?

FlowRunner agents can run Create Contact, Create Meeting, and Connect Contact To Meeting in Idiligo, plus 15 more actions.

Does connecting Idiligo to FlowRunner require OAuth?

No. Idiligo connects to FlowRunner with an API key, no OAuth flow required.

Can Idiligo trigger a FlowRunner workflow automatically?

Yes. Idiligo supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Idiligo

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us