Insightly
App · CRM Systems · 15 actions
Keep Insightly CRM up to date from your workflows: create, update and find contacts, organizations, leads and opportunities, add tasks and notes, and delete records.
Actions
| Action | What it does |
|---|---|
| Add note | Log a note on a contact, organization, lead, opportunity or project. |
| Create contact | Add a person to Insightly, optionally at an organization. |
| Create lead | Add a lead: someone who might become a customer. |
| Create opportunity | Add a deal you're working on, optionally with an organization and a contact. |
| Create organization | Add a company or other organization to Insightly. |
| Create task | Add a to-do, optionally about a contact, organization, lead, opportunity or project. |
| Delete record | Permanently delete a contact, organization, lead, opportunity, project, task or note. |
| Find contacts | Look up contacts by email, name, phone or another field, or by tag. |
| Find leads | Look up leads by email, name, company or phone, or by tag. |
| Find opportunities | Look up deals by name, state or organization, or by tag. |
| Find organizations | Look up organizations by name, website or phone, or by tag. |
| Update contact | Change a contact's details. |
| Update lead | Change a lead's details or status. |
| Update opportunity | Change a deal's details, or mark it won or lost. |
| Update organization | Change an organization's details. |
Add note
Log a note on a contact, organization, lead, opportunity or project.
Inputs
- Record type
record_typetextRequired - What the note is about.One of:
contact,organization,lead,opportunity,project. - Record
record_idtextRequired - Which one. Pick it, or pass its id from an earlier step.
- Title
titletextRequired - A short summary.
- Note
bodytext - The note itself.
Outputs
BODYtext- The note itself.
DATE_CREATED_UTCtext- When it was added (UTC).
NOTE_IDnumber- The note's id.
TITLEtext- Title.
Example output
{
"BODY": "Wants the annual plan; decision by end of quarter.",
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"NOTE_ID": 87654321,
"TITLE": "Discovery call"
}Create contact
Add a person to Insightly, optionally at an organization.
Inputs
- First name
first_nametextRequired - First name.
- Last name
last_nametext - Last name.
- Email
emailtext - Email address.
- Phone
phonetext - Phone number.
- Mobile phone
mobile_phonetext - Mobile phone number.
- Job title
job_titletext - Job title.
- Organization
organization_idtext - The organization. Pick one, or pass an ORGANISATION_ID from an earlier step.
- Background
backgroundtext - Background notes about the contact.
- Birthday
birthdaydate - Date of birth.
- LinkedIn
linkedin_urltext - LinkedIn profile URL.
- Street
streettext - The contact's street address.
- City
citytext - City.
- State
statetext - State, province or region.
- Postal code
postal_codetext - ZIP or postal code.
- Country
countrytext - Country.
- Tags
tagslist - Tags to put on the contact.
- Custom fields
custom_fieldsobject - Values for your own contact fields in Insightly. Fields left empty aren't changed.
Outputs
ADDRESS_MAIL_CITYtext- City.
ADDRESS_MAIL_COUNTRYtext- Country.
ADDRESS_MAIL_POSTCODEtext- Postal code.
ADDRESS_MAIL_STATEtext- State or region.
ADDRESS_MAIL_STREETtext- Street.
BACKGROUNDtext- Background notes.
CONTACT_IDnumber- The contact's id, which Update contact and Add note take.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_OF_BIRTHtext- Date of birth.
DATE_UPDATED_UTCtext- When it was last changed (UTC).
EMAIL_ADDRESStext- Email address.
FIRST_NAMEtext- First name.
LAST_NAMEtext- Last name.
ORGANISATION_IDnumber- The organization the contact works for.
OWNER_USER_IDnumber- The user who owns the record.
PHONEtext- Phone.
PHONE_MOBILEtext- Mobile phone.
SOCIAL_LINKEDINtext- LinkedIn profile.
TAGSlist- The record's tags.
TITLEtext- Job title.
Example output
{
"CONTACT_ID": 312345678,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL_ADDRESS": "ada@example.com",
"FIRST_NAME": "Ada",
"LAST_NAME": "Lovelace",
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0100",
"TAGS": [
{
"TAG_NAME": "customer"
}
],
"TITLE": "Head of Engineering"
}Create lead
Add a lead: someone who might become a customer. Status and source default to your account's defaults.
Inputs
- Last name
last_nametextRequired - Last name.
- First name
first_nametext - First name.
- Email
emailtext - Email address.
- Phone
phonetext - Phone number.
- Company
companytext - The company they work for.
- Job title
job_titletext - Job title.
- Website
websitetext - Website, e.g. https://example.com.
- Industry
industrytext - Industry.
- Employee count
employee_countnumber - How many people the company employs.At least 0.
- Rating
ratingnumber - How promising the lead is, 1 to 5 stars.From 1 to 5.
- Description
descriptiontext - What the lead is about.
- Status
lead_status_idtext - The lead's status. Leave empty for your account's default.
- Source
lead_source_idtext - Where the lead came from. Leave empty for your account's default.
- Assigned to
assigned_totext - The Insightly user responsible for it.
- Street
streettext - The lead's street address.
- City
citytext - City.
- State
statetext - State, province or region.
- Postal code
postal_codetext - ZIP or postal code.
- Country
countrytext - Country.
- Tags
tagslist - Tags to put on the lead.
- Custom fields
custom_fieldsobject - Values for your own lead fields in Insightly. Fields left empty aren't changed.
Outputs
CONVERTEDtrue/false- True once the lead has been converted.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
EMAILtext- Email address.
EMPLOYEE_COUNTnumber- Number of employees.
FIRST_NAMEtext- First name.
INDUSTRYtext- Industry.
LAST_NAMEtext- Last name.
LEAD_DESCRIPTIONtext- Description.
LEAD_IDnumber- The lead's id.
LEAD_RATINGnumber- Rating, 1 to 5.
LEAD_SOURCE_IDnumber- Where the lead came from.
LEAD_STATUS_IDnumber- The lead status.
ORGANISATION_NAMEtext- Company name.
OWNER_USER_IDnumber- The user who owns the record.
PHONEtext- Phone.
RESPONSIBLE_USER_IDnumber- The user the lead is assigned to.
TAGSlist- The record's tags.
TITLEtext- Job title.
WEBSITEtext- Website.
Example output
{
"CONVERTED": false,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL": "grace@example.com",
"FIRST_NAME": "Grace",
"LAST_NAME": "Hopper",
"LEAD_ID": 45678901,
"LEAD_RATING": 4,
"LEAD_SOURCE_ID": 2345678,
"LEAD_STATUS_ID": 3456789,
"ORGANISATION_NAME": "Compilers Inc",
"OWNER_USER_ID": 1234567,
"TAGS": []
}Create opportunity
Add a deal you're working on, optionally with an organization and a contact.
Inputs
- Name
nametextRequired - The opportunity's name.
- Details
detailstext - What the deal is about.
- Organization
organization_idtext - The organization. Pick one, or pass an ORGANISATION_ID from an earlier step.
- Contact
contact_idtext - The main contact for the deal.
- State
statetext - Where the deal stands.One of:
OPEN,WON,LOST,SUSPENDED,ABANDONED. - Value
valuenumber - What the deal is worth (per period, for a per-period bid).At least 0.
- Currency
currencytext - The currency of the value. Leave empty for your account's currency.
- Bid type
bid_typetext - How the value is charged.One of:
Fixed Bid,Per Hour,Per Day,Per Week,Per Month,Per Year. - Bid duration
bid_durationnumber - For a per-period bid, how many periods (e.g. 6 for 6 months).At least 1.
- Probability
probabilitynumber - The chance of winning it, 0 to 100 (%).From 0 to 100.
- Expected close date
forecast_close_datedate - When you expect it to close.
- Category
category_idtext - The opportunity's category.
- Assigned to
assigned_totext - The Insightly user responsible for it.
- Tags
tagslist - Tags to put on the opportunity.
- Custom fields
custom_fieldsobject - Values for your own opportunity fields in Insightly. Fields left empty aren't changed.
Outputs
ACTUAL_CLOSE_DATEtext- When it closed.
BID_AMOUNTnumber- The value of the deal.
BID_CURRENCYtext- Currency code, e.g. USD.
BID_DURATIONnumber- How many hours, days... a per-period bid covers.
BID_TYPEtext- Fixed Bid, or Per Hour, Day, Week, Month or Year.
CATEGORY_IDnumber- Its category.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
FORECAST_CLOSE_DATEtext- When it is expected to close.
OPPORTUNITY_DETAILStext- Details.
OPPORTUNITY_IDnumber- The opportunity's id.
OPPORTUNITY_NAMEtext- Name.
OPPORTUNITY_STATEtext- OPEN, WON, LOST, SUSPENDED or ABANDONED.
OPPORTUNITY_VALUEnumber- The total value Insightly works out.
ORGANISATION_IDnumber- The organization it is with.
OWNER_USER_IDnumber- The user who owns the record.
PIPELINE_IDnumber- Its pipeline.
PROBABILITYnumber- Chance of winning, 0 to 100.
RESPONSIBLE_USER_IDnumber- The user it is assigned to.
STAGE_IDnumber- Its pipeline stage.
TAGSlist- The record's tags.
Example output
{
"BID_AMOUNT": 12000,
"BID_CURRENCY": "USD",
"BID_TYPE": "Fixed Bid",
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"FORECAST_CLOSE_DATE": "2026-12-31 00:00:00",
"OPPORTUNITY_ID": 23456789,
"OPPORTUNITY_NAME": "Analytical Engines - annual plan",
"OPPORTUNITY_STATE": "OPEN",
"OPPORTUNITY_VALUE": 12000,
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PROBABILITY": 60,
"RESPONSIBLE_USER_ID": 1234567,
"TAGS": []
}Create organization
Add a company or other organization to Insightly.
Inputs
- Name
nametextRequired - The organization's name.
- Phone
phonetext - Phone number.
- Website
websitetext - Website, e.g. https://example.com.
- Background
backgroundtext - Background notes about the organization.
- LinkedIn
linkedin_urltext - LinkedIn profile URL.
- Street
streettext - The organization's billing street address.
- City
citytext - City.
- State
statetext - State, province or region.
- Postal code
postal_codetext - ZIP or postal code.
- Country
countrytext - Country.
- Tags
tagslist - Tags to put on the organization.
- Custom fields
custom_fieldsobject - Values for your own organization fields in Insightly. Fields left empty aren't changed.
Outputs
ADDRESS_BILLING_CITYtext- City.
ADDRESS_BILLING_COUNTRYtext- Country.
ADDRESS_BILLING_POSTCODEtext- Postal code.
ADDRESS_BILLING_STATEtext- State or region.
ADDRESS_BILLING_STREETtext- Street.
BACKGROUNDtext- Background notes.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
ORGANISATION_IDnumber- The organization's id, which a contact or opportunity can be linked to.
ORGANISATION_NAMEtext- Name.
OWNER_USER_IDnumber- The user who owns the record.
PHONEtext- Phone.
SOCIAL_LINKEDINtext- LinkedIn page.
TAGSlist- The record's tags.
WEBSITEtext- Website.
Example output
{
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"ORGANISATION_ID": 176543210,
"ORGANISATION_NAME": "Analytical Engines Ltd",
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0101",
"TAGS": [],
"WEBSITE": "https://example.com"
}Create task
Add a to-do, optionally about a contact, organization, lead, opportunity or project. It's assigned to you unless you pick someone else.
Inputs
- Title
titletextRequired - What needs doing.
- Details
detailstext - More detail.
- Due date
due_datedate - When it's due.
- Start date
start_datedate - When to start it.
- Status
statustext - Default: Not started.One of:
NOT STARTED,IN PROGRESS,WAITING,DEFERRED,COMPLETED. - Priority
prioritytext - How urgent it is.One of:
1(Low),2(Medium),3(High). - Category
category_idtext - The task's category.
- Assigned to
assigned_totext - The Insightly user responsible for it.
- Reminder
reminderdate and time - When Insightly should remind the person it's assigned to.
- Related to
related_typetext - What kind of record the task is about, if any.One of:
contact,organization,lead,opportunity,project. - Related record
related_idtext - Which record the task is about.
Outputs
COMPLETEDtrue/false- True once done.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
DETAILStext- Details.
DUE_DATEtext- When it is due.
OPPORTUNITY_IDnumber- The opportunity it is about, if any.
OWNER_USER_IDnumber- The user who owns the record.
PRIORITYnumber- 1 (low), 2 (medium) or 3 (high).
PROJECT_IDnumber- The project it is about, if any.
RESPONSIBLE_USER_IDnumber- The user it is assigned to.
START_DATEtext- When it starts.
STATUStext- NOT STARTED, IN PROGRESS, WAITING, DEFERRED or COMPLETED.
TASK_IDnumber- The task's id.
TITLEtext- Title.
Example output
{
"COMPLETED": false,
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"DUE_DATE": "2026-09-25 00:00:00",
"OWNER_USER_ID": 1234567,
"PRIORITY": 2,
"RESPONSIBLE_USER_ID": 1234567,
"STATUS": "NOT STARTED",
"TASK_ID": 98765432,
"TITLE": "Send Ada the proposal"
}Delete record
Permanently delete a contact, organization, lead, opportunity, project, task or note. Deleting one that's already gone succeeds.
Inputs
- Record type
record_typetextRequired - What to delete.One of:
contact,organization,lead,opportunity,project,task,note. - Record
record_idtextRequired - Which one. Pick it, or pass its id from an earlier step.
Outputs
already_deletedtrue/false- True if it was already gone (Insightly answered 404) rather than deleted by this step.
deletedtrue/false- True once the record is gone.
record_idnumber- The id deleted.
record_typetext- The kind of record deleted.
Example output
{
"already_deleted": false,
"deleted": true,
"record_id": 312345678,
"record_type": "contact"
}Find contacts
Look up contacts by email, name, phone or another field, or by tag.
Inputs
- Search by
search_bytext - The contact field to match. Leave empty to list every contact.One of:
EMAIL_ADDRESS(Email),FIRST_NAME(First name),LAST_NAME(Last name),PHONE,PHONE_MOBILE(Mobile phone),TITLE(Job title),ORGANISATION_ID(Organization ID),TAG. - Value
valuetext - The value to look for. It has to match exactly.
- Changed since
updated_afterdate and time - Only contacts changed after this moment. Can't be combined with a tag search.
- Limit
limitnumber - How many to return, 1 to 500. Default 100.From 1 to 500.
- Skip
skipnumber - Skip this many matches first, to get the next page.At least 0.
Outputs
countnumber- How many contacts matched (in this page).
firstobject- The first matching contact, or empty when none matched. Handy for a follow-up step that updates it.
recordslist- The matching contacts.
Example output
{
"count": 1,
"first": {
"CONTACT_ID": 312345678,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL_ADDRESS": "ada@example.com",
"FIRST_NAME": "Ada",
"LAST_NAME": "Lovelace",
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0100",
"TAGS": [
{
"TAG_NAME": "customer"
}
],
"TITLE": "Head of Engineering"
},
"records": [
{
"CONTACT_ID": 312345678,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL_ADDRESS": "ada@example.com",
"FIRST_NAME": "Ada",
"LAST_NAME": "Lovelace",
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0100",
"TAGS": [
{
"TAG_NAME": "customer"
}
],
"TITLE": "Head of Engineering"
}
]
}Find leads
Look up leads by email, name, company or phone, or by tag.
Inputs
- Search by
search_bytext - The lead field to match. Leave empty to list every lead.One of:
EMAIL,FIRST_NAME(First name),LAST_NAME(Last name),ORGANISATION_NAME(Name),PHONE,TAG. - Value
valuetext - The value to look for. It has to match exactly.
- Changed since
updated_afterdate and time - Only leads changed after this moment. Can't be combined with a tag search.
- Limit
limitnumber - How many to return, 1 to 500. Default 100.From 1 to 500.
- Skip
skipnumber - Skip this many matches first, to get the next page.At least 0.
Outputs
countnumber- How many leads matched (in this page).
firstobject- The first matching lead, or empty when none matched. Handy for a follow-up step that updates it.
recordslist- The matching leads.
Example output
{
"count": 1,
"first": {
"CONVERTED": false,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL": "grace@example.com",
"FIRST_NAME": "Grace",
"LAST_NAME": "Hopper",
"LEAD_ID": 45678901,
"LEAD_RATING": 4,
"LEAD_SOURCE_ID": 2345678,
"LEAD_STATUS_ID": 3456789,
"ORGANISATION_NAME": "Compilers Inc",
"OWNER_USER_ID": 1234567,
"TAGS": []
},
"records": [
{
"CONVERTED": false,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL": "grace@example.com",
"FIRST_NAME": "Grace",
"LAST_NAME": "Hopper",
"LEAD_ID": 45678901,
"LEAD_RATING": 4,
"LEAD_SOURCE_ID": 2345678,
"LEAD_STATUS_ID": 3456789,
"ORGANISATION_NAME": "Compilers Inc",
"OWNER_USER_ID": 1234567,
"TAGS": []
}
]
}Find opportunities
Look up deals by name, state or organization, or by tag.
Inputs
- Search by
search_bytext - The opportunity field to match. Leave empty to list every opportunity.One of:
OPPORTUNITY_NAME(Name),OPPORTUNITY_STATE(State (Open, Won, Lost, Suspended or Abandoned)),ORGANISATION_ID(Organization ID),TAG. - Value
valuetext - The value to look for. It has to match exactly.
- Changed since
updated_afterdate and time - Only opportunities changed after this moment. Can't be combined with a tag search.
- Limit
limitnumber - How many to return, 1 to 500. Default 100.From 1 to 500.
- Skip
skipnumber - Skip this many matches first, to get the next page.At least 0.
Outputs
countnumber- How many opportunities matched (in this page).
firstobject- The first matching opportunity, or empty when none matched. Handy for a follow-up step that updates it.
recordslist- The matching opportunities.
Example output
{
"count": 1,
"first": {
"BID_AMOUNT": 12000,
"BID_CURRENCY": "USD",
"BID_TYPE": "Fixed Bid",
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"FORECAST_CLOSE_DATE": "2026-12-31 00:00:00",
"OPPORTUNITY_ID": 23456789,
"OPPORTUNITY_NAME": "Analytical Engines - annual plan",
"OPPORTUNITY_STATE": "OPEN",
"OPPORTUNITY_VALUE": 12000,
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PROBABILITY": 60,
"RESPONSIBLE_USER_ID": 1234567,
"TAGS": []
},
"records": [
{
"BID_AMOUNT": 12000,
"BID_CURRENCY": "USD",
"BID_TYPE": "Fixed Bid",
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"FORECAST_CLOSE_DATE": "2026-12-31 00:00:00",
"OPPORTUNITY_ID": 23456789,
"OPPORTUNITY_NAME": "Analytical Engines - annual plan",
"OPPORTUNITY_STATE": "OPEN",
"OPPORTUNITY_VALUE": 12000,
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PROBABILITY": 60,
"RESPONSIBLE_USER_ID": 1234567,
"TAGS": []
}
]
}Find organizations
Look up organizations by name, website or phone, or by tag.
Inputs
- Search by
search_bytext - The organization field to match. Leave empty to list every organization.One of:
ORGANISATION_NAME(Name),WEBSITE,PHONE,TAG. - Value
valuetext - The value to look for. It has to match exactly.
- Changed since
updated_afterdate and time - Only organizations changed after this moment. Can't be combined with a tag search.
- Limit
limitnumber - How many to return, 1 to 500. Default 100.From 1 to 500.
- Skip
skipnumber - Skip this many matches first, to get the next page.At least 0.
Outputs
countnumber- How many organizations matched (in this page).
firstobject- The first matching organization, or empty when none matched. Handy for a follow-up step that updates it.
recordslist- The matching organizations.
Example output
{
"count": 1,
"first": {
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"ORGANISATION_ID": 176543210,
"ORGANISATION_NAME": "Analytical Engines Ltd",
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0101",
"TAGS": [],
"WEBSITE": "https://example.com"
},
"records": [
{
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"ORGANISATION_ID": 176543210,
"ORGANISATION_NAME": "Analytical Engines Ltd",
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0101",
"TAGS": [],
"WEBSITE": "https://example.com"
}
]
}Update contact
Change a contact's details. Only the fields you fill in change.
Inputs
- Contact
contact_idtextRequired - The contact. Pick one, or pass a CONTACT_ID from an earlier step.
- First name
first_nametext - First name.
- Last name
last_nametext - Last name.
- Email
emailtext - Email address.
- Phone
phonetext - Phone number.
- Mobile phone
mobile_phonetext - Mobile phone number.
- Job title
job_titletext - Job title.
- Organization
organization_idtext - The organization. Pick one, or pass an ORGANISATION_ID from an earlier step.
- Background
backgroundtext - Background notes about the contact.
- Birthday
birthdaydate - Date of birth.
- LinkedIn
linkedin_urltext - LinkedIn profile URL.
- Street
streettext - The contact's street address.
- City
citytext - City.
- State
statetext - State, province or region.
- Postal code
postal_codetext - ZIP or postal code.
- Country
countrytext - Country.
- Add tags
add_tagslist - Tags to add. The contact's existing tags are kept.
- Custom fields
custom_fieldsobject - Values for your own contact fields in Insightly. Fields left empty aren't changed.
Outputs
ADDRESS_MAIL_CITYtext- City.
ADDRESS_MAIL_COUNTRYtext- Country.
ADDRESS_MAIL_POSTCODEtext- Postal code.
ADDRESS_MAIL_STATEtext- State or region.
ADDRESS_MAIL_STREETtext- Street.
BACKGROUNDtext- Background notes.
CONTACT_IDnumber- The contact's id, which Update contact and Add note take.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_OF_BIRTHtext- Date of birth.
DATE_UPDATED_UTCtext- When it was last changed (UTC).
EMAIL_ADDRESStext- Email address.
FIRST_NAMEtext- First name.
LAST_NAMEtext- Last name.
ORGANISATION_IDnumber- The organization the contact works for.
OWNER_USER_IDnumber- The user who owns the record.
PHONEtext- Phone.
PHONE_MOBILEtext- Mobile phone.
SOCIAL_LINKEDINtext- LinkedIn profile.
TAGSlist- The record's tags.
TITLEtext- Job title.
Example output
{
"CONTACT_ID": 312345678,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL_ADDRESS": "ada@example.com",
"FIRST_NAME": "Ada",
"LAST_NAME": "Lovelace",
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0100",
"TAGS": [
{
"TAG_NAME": "customer"
}
],
"TITLE": "Head of Engineering"
}Update lead
Change a lead's details or status. Only the fields you fill in change.
Inputs
- Lead
lead_idtextRequired - The lead. Pick one, or pass a LEAD_ID from an earlier step.
- Last name
last_nametext - Last name.
- First name
first_nametext - First name.
- Email
emailtext - Email address.
- Phone
phonetext - Phone number.
- Company
companytext - The company they work for.
- Job title
job_titletext - Job title.
- Website
websitetext - Website, e.g. https://example.com.
- Industry
industrytext - Industry.
- Employee count
employee_countnumber - How many people the company employs.At least 0.
- Rating
ratingnumber - How promising the lead is, 1 to 5 stars.From 1 to 5.
- Description
descriptiontext - What the lead is about.
- Status
lead_status_idtext - The lead's status. Leave empty for your account's default.
- Source
lead_source_idtext - Where the lead came from. Leave empty for your account's default.
- Assigned to
assigned_totext - The Insightly user responsible for it.
- Street
streettext - The lead's street address.
- City
citytext - City.
- State
statetext - State, province or region.
- Postal code
postal_codetext - ZIP or postal code.
- Country
countrytext - Country.
- Add tags
add_tagslist - Tags to add. The lead's existing tags are kept.
- Custom fields
custom_fieldsobject - Values for your own lead fields in Insightly. Fields left empty aren't changed.
Outputs
CONVERTEDtrue/false- True once the lead has been converted.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
EMAILtext- Email address.
EMPLOYEE_COUNTnumber- Number of employees.
FIRST_NAMEtext- First name.
INDUSTRYtext- Industry.
LAST_NAMEtext- Last name.
LEAD_DESCRIPTIONtext- Description.
LEAD_IDnumber- The lead's id.
LEAD_RATINGnumber- Rating, 1 to 5.
LEAD_SOURCE_IDnumber- Where the lead came from.
LEAD_STATUS_IDnumber- The lead status.
ORGANISATION_NAMEtext- Company name.
OWNER_USER_IDnumber- The user who owns the record.
PHONEtext- Phone.
RESPONSIBLE_USER_IDnumber- The user the lead is assigned to.
TAGSlist- The record's tags.
TITLEtext- Job title.
WEBSITEtext- Website.
Example output
{
"CONVERTED": false,
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"EMAIL": "grace@example.com",
"FIRST_NAME": "Grace",
"LAST_NAME": "Hopper",
"LEAD_ID": 45678901,
"LEAD_RATING": 4,
"LEAD_SOURCE_ID": 2345678,
"LEAD_STATUS_ID": 3456789,
"ORGANISATION_NAME": "Compilers Inc",
"OWNER_USER_ID": 1234567,
"TAGS": []
}Update opportunity
Change a deal's details, or mark it won or lost. Only the fields you fill in change.
Inputs
- Opportunity
opportunity_idtextRequired - The opportunity. Pick one, or pass an OPPORTUNITY_ID from an earlier step.
- Name
nametext - The opportunity's name.
- Details
detailstext - What the deal is about.
- Organization
organization_idtext - The organization. Pick one, or pass an ORGANISATION_ID from an earlier step.
- State
statetext - Where the deal stands.One of:
OPEN,WON,LOST,SUSPENDED,ABANDONED. - Value
valuenumber - What the deal is worth (per period, for a per-period bid).At least 0.
- Currency
currencytext - The currency of the value. Leave empty for your account's currency.
- Bid type
bid_typetext - How the value is charged.One of:
Fixed Bid,Per Hour,Per Day,Per Week,Per Month,Per Year. - Bid duration
bid_durationnumber - For a per-period bid, how many periods (e.g. 6 for 6 months).At least 1.
- Probability
probabilitynumber - The chance of winning it, 0 to 100 (%).From 0 to 100.
- Expected close date
forecast_close_datedate - When you expect it to close.
- Category
category_idtext - The opportunity's category.
- Assigned to
assigned_totext - The Insightly user responsible for it.
- Add tags
add_tagslist - Tags to add. The opportunity's existing tags are kept.
- Custom fields
custom_fieldsobject - Values for your own opportunity fields in Insightly. Fields left empty aren't changed.
Outputs
ACTUAL_CLOSE_DATEtext- When it closed.
BID_AMOUNTnumber- The value of the deal.
BID_CURRENCYtext- Currency code, e.g. USD.
BID_DURATIONnumber- How many hours, days... a per-period bid covers.
BID_TYPEtext- Fixed Bid, or Per Hour, Day, Week, Month or Year.
CATEGORY_IDnumber- Its category.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
FORECAST_CLOSE_DATEtext- When it is expected to close.
OPPORTUNITY_DETAILStext- Details.
OPPORTUNITY_IDnumber- The opportunity's id.
OPPORTUNITY_NAMEtext- Name.
OPPORTUNITY_STATEtext- OPEN, WON, LOST, SUSPENDED or ABANDONED.
OPPORTUNITY_VALUEnumber- The total value Insightly works out.
ORGANISATION_IDnumber- The organization it is with.
OWNER_USER_IDnumber- The user who owns the record.
PIPELINE_IDnumber- Its pipeline.
PROBABILITYnumber- Chance of winning, 0 to 100.
RESPONSIBLE_USER_IDnumber- The user it is assigned to.
STAGE_IDnumber- Its pipeline stage.
TAGSlist- The record's tags.
Example output
{
"BID_AMOUNT": 12000,
"BID_CURRENCY": "USD",
"BID_TYPE": "Fixed Bid",
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"FORECAST_CLOSE_DATE": "2026-12-31 00:00:00",
"OPPORTUNITY_ID": 23456789,
"OPPORTUNITY_NAME": "Analytical Engines - annual plan",
"OPPORTUNITY_STATE": "OPEN",
"OPPORTUNITY_VALUE": 12000,
"ORGANISATION_ID": 176543210,
"OWNER_USER_ID": 1234567,
"PROBABILITY": 60,
"RESPONSIBLE_USER_ID": 1234567,
"TAGS": []
}Update organization
Change an organization's details. Only the fields you fill in change.
Inputs
- Organization
organization_idtextRequired - The organization. Pick one, or pass an ORGANISATION_ID from an earlier step.
- Name
nametext - The organization's name.
- Phone
phonetext - Phone number.
- Website
websitetext - Website, e.g. https://example.com.
- Background
backgroundtext - Background notes about the organization.
- LinkedIn
linkedin_urltext - LinkedIn profile URL.
- Street
streettext - The organization's billing street address.
- City
citytext - City.
- State
statetext - State, province or region.
- Postal code
postal_codetext - ZIP or postal code.
- Country
countrytext - Country.
- Add tags
add_tagslist - Tags to add. The organization's existing tags are kept.
- Custom fields
custom_fieldsobject - Values for your own organization fields in Insightly. Fields left empty aren't changed.
Outputs
ADDRESS_BILLING_CITYtext- City.
ADDRESS_BILLING_COUNTRYtext- Country.
ADDRESS_BILLING_POSTCODEtext- Postal code.
ADDRESS_BILLING_STATEtext- State or region.
ADDRESS_BILLING_STREETtext- Street.
BACKGROUNDtext- Background notes.
CUSTOMFIELDSlist- The record's custom field values.
DATE_CREATED_UTCtext- When it was created (UTC).
DATE_UPDATED_UTCtext- When it was last changed (UTC).
ORGANISATION_IDnumber- The organization's id, which a contact or opportunity can be linked to.
ORGANISATION_NAMEtext- Name.
OWNER_USER_IDnumber- The user who owns the record.
PHONEtext- Phone.
SOCIAL_LINKEDINtext- LinkedIn page.
TAGSlist- The record's tags.
WEBSITEtext- Website.
Example output
{
"CUSTOMFIELDS": [],
"DATE_CREATED_UTC": "2026-09-21 16:42:49",
"DATE_UPDATED_UTC": "2026-09-21 16:42:49",
"ORGANISATION_ID": 176543210,
"ORGANISATION_NAME": "Analytical Engines Ltd",
"OWNER_USER_ID": 1234567,
"PHONE": "+1 415 555 0101",
"TAGS": [],
"WEBSITE": "https://example.com"
}