FlowRunner
PricingContact
Theme
Start Free

Insightly

CRM

Connect AI agents to Insightly CRM. Agents manage contacts, organizations, opportunities, projects, leads, tasks, calendar events, and notes across 39 actions, with pipeline and stage reference data for advancing deals.

39 actions Basic auth available
Insightly website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
Stripe confirms payment on a deal the rep has been working
Agent pulls buyer, order value, and line details from the payment
List Pipelines and List Pipeline Stages resolve the correct stage IDs
Update Opportunity marks the deal Won at the right pipeline stage
Create Project and Create Task stand up the delivery plan
Delivery owner gets a Slack message with the project link
Owner confirms scope before kickoff tasks go to the team

What This Integration Enables

Insightly is built for teams whose work does not end at Closed Won. It is the rare CRM that carries a deal into delivery, with Projects sitting next to Opportunities in the same system. That is exactly where most automation drops the ball: the sale closes, and the handoff to delivery happens over chat and memory. FlowRunner agents close that gap. They advance opportunities through real pipeline stages, spin up the project and its tasks the moment a deal is won, and keep the activity history honest with events and notes on the record. The connector covers contacts, organisations, opportunities, projects, leads, tasks, calendar events, and notes, plus the reference data that keeps writes valid: List Users, List Pipelines, and List Pipeline Stages supply the IDs an agent needs so a stage move lands on a real stage, not a guess. And because this is a [human-in-the-loop](/concepts/human-in-the-loop/) platform, the operations that cannot be undone stay behind a person's decision.

Without FlowRunner

Won deals stall at handoff The rep announces the win in chat and delivery finds out days later
Retyped project setup Someone rebuilds the deal details into a project by hand
Stale pipeline stages Deals sit in the wrong stage because nobody updates the CRM after payment

With FlowRunner

Same-day delivery kickoff The project and its first tasks exist the moment payment clears
One linked record Deal, project, tasks, events, and notes stay attached to the same organisation
Pipeline reflects reality Stage moves happen when the money moves, not when someone remembers

Use Case Scenarios

Won deal to delivery, without the gap

A rep closes a deal and the customer pays through [Stripe](/integrations/stripe). The agent finds the matching opportunity, resolves the pipeline with List Pipeline Stages, and calls Update Opportunity to mark it Won at the correct stage. It then creates the delivery project with Create Project, seeds the first sprint with Create Task, and posts the project link to the delivery channel in [Slack](/integrations/slack). The delivery lead confirms scope in the thread, and the team starts with the full deal context already attached to the organisation.

Meetings and leads that log themselves

A prospect books time through [Calendly](/integrations/calendly). The agent creates the lead with Create Lead, adds the booking to the CRM calendar with Create Event, and records the meeting context with Create Note so the rep walks in prepared. A follow-up lands on the rep's list through Create Task. When a lead originates in [HubSpot](/integrations/hubspot) instead, the agent mirrors it with Create Contact and routes it by source and status. Nothing about the prospect's journey depends on a rep remembering to type it in.

Pipeline reporting the sales lead does not have to build

On a schedule, the agent runs List Opportunities filtered to open deals, writes the pipeline into a report with [Google Sheets](/integrations/google-sheets), and posts a summary to the sales channel in Slack. Deals missing a close date or sitting in an early stage past their usual dwell time get called out by name. The sales lead reads the exceptions, not the export.

Human-in-Loop Highlight

Insightly's Delete Contact and Delete Organisation are permanent. The API is explicit: these actions cannot be undone, and an organisation takes its linked history with it. So when a dedup agent finds two organisations for the same company, one holding the open opportunity and twelve notes, the other holding the delivery project, it does not pick a survivor. It gathers the evidence with Get Organisation and Search Contacts, relinks nothing, deletes nothing, and asks the CRM owner in Slack: "Two organisations match Acme Industrial. ORG 4417 carries the open opportunity and the note history. ORG 5120 carries the delivery project. Which record survives?" Only after the answer does the agent move the linked records to the survivor and call Delete Organisation on the duplicate. The judgment call stays human because the undo button does not exist.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

39 actions

Contacts

6
  • List Contacts Retrieves a paginated list of contacts with field-level filters. Used to sweep for records matching a domain, owner, or custom field.
  • Get Contact Retrieves a single contact with all standard fields, custom fields, links, and tags. Used to load full context before an update or merge decision.
  • Create Contact Creates a new contact, optionally linked to an organisation. Used when orders, form fills, or meetings introduce a new person.
  • Update Contact Changes only the fields supplied, leaving the rest untouched. Used to enrich or correct records without clobbering existing data.
  • Delete Contact Permanently deletes a contact. Cannot be undone, so agents put this behind a human decision.
  • Search Contacts Searches contacts by a single standard or custom field, such as EMAIL_ADDRESS. Used as the duplicate check before any create.

Organisations

5
  • List Organisations Retrieves a paginated list of organisations with field filters. Used for account sweeps and match checks.
  • Get Organisation Retrieves a single organisation with addresses, links, and tags. Used to load the full picture before merge or update decisions.
  • Create Organisation Creates a new organisation from a name plus optional phone, website, and background. Used when a new company enters the pipeline.
  • Update Organisation Updates supplied fields on an existing organisation. Used for enrichment and ownership changes.
  • Delete Organisation Permanently deletes an organisation. Cannot be undone; reserved for human-approved cleanup.

Opportunities

5
  • List Opportunities Retrieves a paginated list of deals with filters. Used for pipeline reports and stale-deal sweeps.
  • Get Opportunity Retrieves a single deal including pipeline and stage. Used to confirm current state before a move.
  • Create Opportunity Creates a deal with state, value, currency, and probability. Used when orders or qualified leads open new business.
  • Update Opportunity Moves deals through pipeline stages or marks them Won or Lost. The workhorse for keeping the pipeline true.
  • Delete Opportunity Permanently deletes a deal. Cannot be undone; agents propose it, people approve it.

Projects

5
  • List Projects Retrieves projects with status filters. Used to monitor delivery workload.
  • Get Project Retrieves a single project with status and custom fields. Used to check delivery state before downstream steps.
  • Create Project Creates a project with status and details. Used the moment a deal is won to start delivery.
  • Update Project Changes project status or details. Used to keep delivery state current as milestones complete.
  • Delete Project Permanently deletes a project. Cannot be undone; gated behind human sign-off.

Leads

5
  • List Leads Retrieves leads with filters by status or source. Used for routing and follow-up sweeps.
  • Get Lead Retrieves a single lead with status and custom fields. Used before qualification decisions.
  • Create Lead Creates a lead from a name plus contact details and company. Used to capture inbound interest from any channel.
  • Update Lead Moves a lead through statuses or corrects details. Used as qualification progresses.
  • Delete Lead Permanently deletes a lead. Cannot be undone; kept behind approval.

Tasks, Events, and Notes

10
  • List Tasks Retrieves tasks with status filters. Used to audit open follow-ups.
  • Get Task Retrieves a single task with priority and due date. Used before reassignment or completion.
  • Create Task Creates a task with status, priority, and due date. Used to put follow-ups on a real list instead of in someone's head.
  • Update Task Marks tasks complete or shifts due dates. Used as work finishes or priorities move.
  • Delete Task Permanently deletes a task. Cannot be undone.
  • List Events Retrieves calendar events. Used to review scheduled activity on a record.
  • Get Event Retrieves a single event with times, location, and links. Used to load meeting context.
  • Create Event Creates a calendar event with start and end times. Used to log bookings from scheduling tools into the CRM calendar.
  • List Notes Retrieves notes attached to records. Used to gather activity history before decisions.
  • Create Note Creates a note linked to a parent record. Used to preserve meeting context and agent decisions on the record.

Reference Data

3
  • List Users Retrieves account users with their IDs. Used to assign owners and responsible parties correctly.
  • List Pipelines Retrieves all pipelines with their record type. Used so opportunity and project writes target the right pipeline.
  • List Pipeline Stages Retrieves all stages with their pipeline and order. Used so every stage move lands on a real stage ID.

Frequently Asked Questions

What can FlowRunner do with Insightly?

FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Insightly, plus 36 more actions.

Does connecting Insightly to FlowRunner require OAuth?

No. Insightly connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Insightly trigger a FlowRunner workflow automatically?

Insightly doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Insightly

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