Submit a request

How can we help?

Articles in this section

AppConnect Recipe Library by App

Updated

Ready-to-use recipes by integration. For general AppConnect mechanics (triggers, actions, variables, and the seven worked walkthroughs), see AppConnect Recipe Examples.

18 recipes across eight integrations. Each states its connections, trigger, action, objective and logic, at the level of what the recipe does rather than click-by-click.

On this page:

Google Workspace

Google Workspace is Google’s suite of productivity and collaboration tools. Use the recipes below as starting points for your own recipes with the Google integrations.

Recipe #1 When a Lead is Created, send an email through Gmail

  • Connections: Gmail, Insightly
  • Trigger: A new lead is created in Insightly
  • Action: Send an email through Gmail

When a new lead has been created in Insightly, send an email through Gmail.

Recipe logic:

  1. The recipe will be triggered when a new lead has been created in Insightly.
  2. Populate the To field by pulling the Email Address data pill from step 1.
  3. Populate the From field by pulling the Lead Owner data pill from step 1.

Recipe #2 When a New Task is Created in Insightly, Create a Task in Google Calendar

  • Connections: Google Calendar, Insightly
  • Trigger: A new task is created in Insightly
  • Action: Create a task in Google Calendar

When a new task has been created in Insightly, create a task in Google Calendar that includes the Insightly task’s name, description, and date due.

Recipe logic:

  1. The recipe will be triggered when a new task has been created in Insightly.
  2. Create a task in Google Calendar.
  3. Pull the Task Name, Description, and Date Due data pills from step 1.

Recipe #3 When an Email is Received in Gmail, Add the Body of the Email to the Contact’s Description

  • Connections: Gmail, Insightly
  • Trigger: An email is received in Gmail
  • Action: Find contact with matching email address and add the body of the email to the contact’s description field.

When an email is received in Gmail, check the sender’s email address. If there is a contact within Insightly with a matching email address, download the email body as plain text, then update the contact’s description field with that text.

Recipe logic:

  1. The recipe will be triggered when an email is received in Gmail.
  2. Search contact records for an email address that matches the email address of the email’s sender.
  3. If a contact is found, download the body of the email.
  4. Update the contact’s Description field with the Body as plain text data pill.
Automated Gmail Welcome Email Workflow Setup — This shows a two-step automation workflow where a new entity created in Insightly real-time triggers an automatic welcome email sent via Gmail to the lead owner. This would help readers understand how to configure automated email notifications so new leads or contacts receive an immediate response without manual effort.
Insightly to Google Calendar Task Automation Workflow — This image shows a two-step automation workflow where a new task created in Insightly automatically creates a corresponding task in Google Calendar, including the task’s name, description, and due date. This integration helps users keep their Insightly tasks and Google Calendar synchronized in real time without manual data entry.

Xero

Xero is accounting software used to automate bookkeeping functions like invoicing and payroll. Use the recipes below as starting points for your own Xero recipes.

Recipe #1 Create Xero Invoice

  • Connections: Xero Shopify (Optional)
  • Trigger: Project created by Shopify or project pipeline stage is reached (project closed)
  • Action: Create an invoice in Xero with products data

When a project has been created from the Shopify integration or a project pipeline stage has been reached, create an invoice using the project data and the linked project product’s data. Once the invoice is created, update the project record with invoice data and status.

Recipe logic:

  1. Project data is the recipe trigger.
  2. Extract the linked project product’s data.
  3. Extract the linked contact data.
  4. Create an invoice with the status of “Submitted” with each line item from the project product’s data. If it’s a Shopify order, the invoice number and the invoice date will be inputted from the project data.
  5. Update the project with invoice date and invoice number.
  6. If it’s a Shopify order, the invoice number and the invoice date will be inputted from the project data.

Recipe #2 Paid Invoice Updates Insightly Project

  • Connections: Xero
  • Trigger: Xero invoice is paid
  • Action: Update matching product status and the date paid

When an invoice is paid in Xero, find the matching project via the invoice id. Update the project status to complete and mark the date paid field.

Recipe logic:

  1. User pays invoice through Xero.
  2. A paid invoice webhook is sent to AppConnect.
  3. Extract the invoice number and search for the matching project.
  4. Update the project status as complete and add in the date paid field.

Recipe #3 Product Sync - Insightly to Xero

  • Connections: Xero Shopify
  • Trigger: Insightly product is created or updated
  • Action: Create or update item in Xero

When a product is created or updated in Insightly via the Shopify integration, create or update the matching item in Xero.

Recipe logic:

  1. Product data is the recipe trigger.
  2. Extract product Xero code.
  3. If Xero code exists, update item in Xero with pre-determined fields.
  4. If Xero code does not exist, create item in Xero with pre-determined fields.
Workato Recipe for Creating Xero Invoices — This image shows a multi-step Workato automation recipe that triggers from Insightly to create invoices in Xero, including logic for finding or creating contacts, building line items, and updating project records with the resulting invoice ID. It would help readers understand the full automated workflow connecting Insightly projects to Xero billing.

1 Workato Recipe for Creating Xero Invoices

 Workato Recipe Linking Xero Invoices to Insightly Projects — This image shows an automated workflow recipe that triggers when an invoice is created or updated in Xero, searches for a matching project in Insightly by Invoice ID, and updates that project with payment data if a match is found. This matters because it illustrates how paid invoices in Xero can automatically mark corresponding projects as complete in Insightly without manual intervention.

2 Workato Recipe Linking Xero Invoices to Insightly Projects

 Workato Recipe for Insightly to Xero Product Sync — This image shows a Workato automation recipe that syncs product data from Insightly CRM to Xero by searching for existing items and either updating them or creating new ones. It includes error handling logic that stops the job silently if a duplicate exists, or stops with an error for other failures.

3 Workato Recipe for Insightly to Xero Product Sync

DocuSign

DocuSign is used to sign documents and agreements electronically from almost any device. Use the recipes below as starting points for your own DocuSign recipes.

Recipe #1 Calendly to Insightly to Docusign

  • Connections: Calendly DocuSign
  • Trigger: Calendly Event Registered
  • Action: Event data sent over from Calendly to Insightly and linked to correct Lead

When Calendly event data is registered, the trigger will send the data into Insightly. Insightly will then check the email address in the payload for a lead. If a lead is found, the information will update. Otherwise, the lead will be created and immediately converted into an opportunity.

Recipe logic:

  1. Trigger event will be when a contact schedules an event through Calendly.
  2. The recipe will then use the email address to look for a lead in Insightly. If no lead is found then a lead will be created.
  3. Lead will immediately be converted into an opportunity and put into stage one of the pipeline.
  4. The function will then connect with Docusign and send out the document.

Recipe #2 Docusign updates opportunity pipeline stage

  • Connections: DocuSign
  • Trigger: A document sent from the recipe is signed.
  • Action: The function will find the associated opportunity via email address in the DocuSign payload and update its pipeline stage to Document Signed.

Once a document from the recipe is signed, the function will use the payload data to find the correct Opportunity and update its pipeline stage to Document signed.

Recipe logic:

  1. The function will trigger when the document is completed.
  2. The function will then find the connected opportunity and update its pipeline stage to Document Signed.
Calendly to Insightly Automation Workflow Steps — This image shows a three-step automation workflow where a new Calendly event triggers a search for matching Insightly records, followed by a conditional check to see if a Record ID from that search is present. This workflow would matter to readers setting up real-time contact or lead creation in Insightly whenever a new meeting is booked in Calendly.

1 Calendly to Insightly Automation Workflow Steps

 Workflow Automation Branch Logic Example — This image shows a workflow automation sequence where a “Yes” path triggers one “Create a new entity” action (step 4), while the “Else” branch executes two consecutive “Create a new entity” actions (steps 6 and 7) before ending. This illustrates how conditional branching in Insightly workflows can perform different numbers of actions depending on whether a condition is met or not.

2 Workflow Automation Branch Logic Example
DocuSign to Insightly Automation Workflow Steps — This image shows a multi-step automation workflow that triggers when a new DocuSign document event occurs, checks if a specific envelope ID matches and its status is “completed,” then searches for matching entities in Insightly CRM. This would help users understand how to set up conditional logic to automatically find and update CRM records when a DocuSign envelope is signed.

3 DocuSign to Insightly Automation Workflow Steps

 Workato Recipe Steps 5-8 with DocuSign Integration — This image shows the final steps of an automated workflow recipe, where the pipeline stage is updated via HTTP, documents are listed in DocuSign, and a sub-recipe is called to upload documents to an Opportunity before the job stops. This would help a user understand how the automation connects Insightly CRM with DocuSign to handle document management as part of a pipeline stage change.

4 Workato Recipe Steps 5-8 with DocuSign Integration

RingCentral

RingCentral is a communications app covering voice, fax, text, conferencing, and web meetings. Use the recipes below as starting points for your own RingCentral recipes.

Recipe #1 Log a call event in Insightly

  • Connections: RingCentral
  • Trigger: RingCentral call has ended
  • Action: Log a call event in Insightly

When a RingCentral call has ended, log a call event in Insightly.

Recipe logic:

  1. The recipe will be triggered when a call has ended in RingCentral.
  2. Based on the direction of the call, inbound or outbound, search for a contact in Insightly via their phone number.
  3. If a matching contact is not found, search for a lead in Insightly via their phone number.
  4. If a lead is not found, create a contact in Insightly using the First Name field (first_name) pulled from the phone number from RingCentral.
  5. Based on the direction of the call, search for a contact/user in Insightly.
  6. Create a new call event record in Insightly with today’s date, link the contact, lead, and contact/user. Call Event is a custom object built prior to building this recipe.

Recipe #2 Update contact’s last called on date

  • Connections: RingCentral
  • Trigger: RingCentral call has ended
  • Action: Update the contact record with the last called on date

When a call has ended, update the contact record with the last called on date.

Recipe logic:

  1. The recipe will be triggered when a call has ended in RingCentral.
  2. Based on the direction of the call, inbound or outbound, search for a contact in Insightly via their phone number.
  3. If no contacts are found, stop the job.
  4. Update Contact’s Last Called On Date field. The Contact’s Last Called On Date custom date field has been built prior to building this recipe.
RingCentral Call-End Automation Workflow in Zapier — This image shows a Zapier automation that triggers when a call ends in RingCentral, then searches Insightly for matching Contacts by phone number, and if none are found, searches for matching Leads instead. This workflow helps teams automatically log or route call activity to the correct record type in Insightly without manual lookup.

1 RingCentral Call-End Automation Workflow in Zapier

 Workflow Steps 6-8 With Branching Logic — This image shows the final steps of an automated workflow in Insightly, where a conditional branch either creates a new entity or skips ahead, then searches for a User_Contact record, and finally creates a new Call Event before ending. This would help a reader understand how the workflow handles both paths of a Yes/No decision and what actions follow regardless of that outcome.

2 Workflow Steps 6-8 With Branching Logic

 RingCentral Call Automation Workflow in Insightly — This image shows a five-step Insightly automation that triggers when a call ends in RingCentral, searches for a matching contact by phone number, stops the workflow if no contact is found, and updates the contact’s Last_Called_On date if one exists. This workflow would help support article readers understand how to automatically log call activity to CRM contacts without manual data entry.

3 RingCentral Call Automation Workflow in Insightly

Zoom

Zoom is a video communications app used to set up virtual video and audio conferencing, webinars, and screen-sharing. Use the recipes below as starting points for your own Zoom recipes.

Recipe #1 Register New Leads for Webinar

  • Connections: Zoom, Google Calendar
  • Trigger: A lead is created in Insightly.
  • Action: Register the lead for a Zoom webinar.

When a lead is created in Insightly, this recipe will register the lead for a Zoom Webinar.

Recipe logic:

  1. The recipe will be triggered when a lead is created in Insightly.
  2. Select the Add registrant action for the Zoom app. Under setup, select Webinar from the Event dropdown, then enter the webinar ID. Pull the email, first name, and last name from step one.
  3. Search for the webinar event in Google Calendar.
  4. Add the attendee to the Google Calendar event using the email address in step one for the attendee email field.

Recipe #2 Track Event Attendance

  • Connections: Zoom
  • Trigger: Zoom webinar ends.
  • Action: Add tags to webinar attendees and webinar absentees.

When a Zoom webinar has ended, add the following tags to Insightly leads who registered and attended: Join Time, Leave Time, and Attentiveness Score. If a lead registered, but did not attend the webinar, tag them as Absent from Webinar.

Recipe logic:

  1. The recipe will be triggered when a Zoom webinar has ended.
  2. Pull all webinar attendees.
  3. If the number of attendees is greater than zero, add the following tags to their associated lead record in Insightly: Join Time, Leave Time, and Attentiveness Score.
  4. Pull all webinar absentees.
  5. If the number of absentees is greater than zero, add the following tags to their associated lead record in Insightly: Absent from Webinar (custom field).
Insightly to Zoom Webinar Automation Workflow — This image shows a four-step automated workflow that triggers when a new lead is created in Insightly, then registers that lead as a Zoom webinar attendee, and finally adds them to the corresponding Google Calendar event. This automation is useful for teams who want to streamline webinar registration without manually syncing contacts across multiple platforms.

1 Insightly to Zoom Webinar Automation Workflow

 Zoom Webinar Automation Workflow in Insightly — This image shows a multi-step automated workflow that triggers when a Zoom webinar ends, retrieves attendees and absentees, and applies tags to contacts based on their participation. It helps users understand how to automatically segment webinar attendees versus no-shows in Insightly CRM using conditional logic.

2 Zoom Webinar Automation Workflow in Insightly

Sage

Sage covers business analysis, insights, and cash flow management. Connected to AppConnect, it can help prevent duplicate orders, accidental deletions, and processing delays. Use the recipes below as starting points for your own Sage recipes.

Recipe #1 SFTP Opportunity Trigger

  • Connections: SFTP Sage Intacct
  • Trigger: Opportunity Created.
  • Action: Update trigger with trigger condition based on Opportunity Stage.

This recipe establishes connectivity between Sage Intacct and Insightly through SFTP.

Recipe logic:

  1. From Insightly, pull the data from the Opportunity object to identify key information from the relational Organization/Account and Contact Records.
  2. Properly prepare data for Sage 100 consumption (may differ based on the connector approach).
  3. Update txt/CSV file on SFTP site to allow Sage 100 services to pick up the file for updating/creating customer/Account/Invoice objects in Sage100.

Recipe #2 Sage to Insightly

  • Connections: Sage Intacct
  • Trigger: An invoice is created in Sage.
  • Action: Update existing record or create new record.

When an invoice is created in Sage, AppConnect will search Insightly for an associated email address in opportunities, organizations, and contacts. If a match is found, the record will be updated. If not, a new record will be created.

Recipe logic:

  1. From the Sage SFTP site, pull new invoice information (provided in txt/csv format) and cycle through the file to identify the corresponding opportunity to map to within Insightly.
  2. Update the Opportunity/Customer/Organization/Account information in Insightly based on the data provided in the mapping document.
Workflow Automation Steps for Organization ID — The image shows two sequential steps in an Insightly workflow: step 3 logs a message to retrieve the Organization ID from a triggering opportunity, and step 4 creates a variable to store that Organization ID for potential future use. This would matter to readers setting up automated workflows that need to capture and reuse organization data across multiple actions.

1 Workflow Automation Steps for Organization ID

 Insightly Automation Steps for Organization Contacts — The image shows three sequential automation workflow steps in Insightly CRM: retrieving an organization’s details, finding all contacts linked to that organization, and then looping through each contact using a “For Each” iterator. This would be relevant to someone building an automated workflow that needs to process or act on every contact associated with a specific organization.

2 Insightly Automation Steps for Organization Contacts

 Workflow Steps 8 Through 10 in Automation — This image shows three sequential automation steps: composing a CSV file, uploading it to an SFTP server, and then querying Insightly to find opportunity line items associated with a related opportunity. These steps illustrate how data is exported and then used to retrieve linked records within a larger automated workflow.

3 Workflow Steps 8 Through 10 in Automation
For Each Loop Uploading Entities to SFTP — This shows a workflow automation loop that iterates over each entity from a previous step, composes a CSV file, and uploads it to an SFTP server. This would be relevant to someone setting up an automated data export process from Insightly CRM to an external file server.

4 For Each Loop Uploading Entities to SFTP

 Sage Intacct Invoice Automation Workflow Steps — The image shows a three-step automation workflow that triggers when a new invoice is created in Sage Intacct, then finds related entities by a field value, and conditionally checks if a user email property is present. This workflow would help readers understand how to set up conditional invoice-based automations that connect Sage Intacct with Insightly CRM.

5 Sage Intacct Invoice Automation Workflow Steps

 Conditional Logic for Creating or Updating Records — This shows a workflow branching where a “Yes” path updates an existing entity and an “Else” path creates a new entity in Insightly. This matters because it illustrates how automation handles duplicate records by choosing the appropriate action based on whether a matching record already exists.

6 Conditional Logic for Creating or Updating Records

Shopify

Shopify is subscription software for setting up an online store and selling products. Use the recipes below as starting points for your own Shopify recipes.

Recipe #1 Add tags to a contact when a checkout has been abandoned

  • Connections: Shopify
  • Trigger: New/Updated abandoned checkout
  • Action: Look for an existing contact. Add tags.

When an abandoned checkout is detected, this recipe will search for an existing contact in Insightly that matches it. If one is found, a tag will be added onto that contact. If it is not an existing contact yet, it will create one in Insightly.

Recipe logic:

  1. The recipe will be triggered when a new or updated abandoned checkout is detected in Shopify.
  2. Search/create an Insightly contact based on the Shopify customer’s email.
  3. The contact will be assigned a tag.

Recipe #2 Add tags to new and returning customers

  • Connections: Shopify
  • Trigger: New order
  • Action: Update contact

Whenever an order has been placed, update the associated contact in Insightly as a returning customer or create a new contact in Insightly if one does not. exist.

Recipe logic:

  1. The recipe will be triggered when a new order has been placed in Shopify.
  2. Search/create an Insightly contact based on the Shopify customer’s email.
  3. If the contact does not exist, create a new contact and add the tag ‘New Customer’.
  4. If the contact already exists and has the ‘Returning Customer’ tag, the job will stop.
  5. If the contact already exists and has the ‘New Customer’ tag, that tag will be replaced with the ‘Returning Customer’ tag.
Shopify Abandoned Checkout to Insightly Contact Lookup — This shows an automation workflow that triggers when a new or updated abandoned checkout occurs in Shopify, then searches for a matching Insightly contact by email address. A conditional step checks whether that email was found, which would allow the workflow to handle new versus existing contacts differently.

1 Shopify Abandoned Checkout to Insightly Contact Lookup

 Conditional Contact Creation and Tag Search Steps — The workflow shows step 4 creating a new Contact entity when a “No” condition is met, and step 5 searching for all Contact records tagged as “Abandoned.” This matters because it illustrates how Insightly automation handles both new contact creation and targeted filtering of contacts by tag value within the same workflow.

2 Conditional Contact Creation and Tag Search Steps

 Conditional Tag Check with Stop and Add Steps — This workflow shows a three-step logic sequence where the automation checks if a “Step 5” tag is absent on a contact, stops the job with an error if the tag is already present, or adds the tag if it is not. This pattern is useful for preventing duplicate tagging and ensuring contacts are only tagged once at a given stage.

3 Conditional Tag Check with Stop and Add Steps
Shopify Order Trigger with Insightly Action — This shows a two-step automation workflow where a new Shopify order acts as the trigger, followed by an Insightly action that finds all matching entities by a field value. This would help readers understand how to connect Shopify sales data to CRM records automatically.

4 Shopify Order Trigger with Insightly Action

 Conditional Logic for Tagging Returning Customers — This shows a workflow automation step that checks if an email from Step 2 is present, and if not, updates the contact record by adding a “Returning Customer” tag. This branching logic helps users understand how to automatically categorize contacts based on data conditions in Insightly.

5 Conditional Logic for Tagging Returning Customers

 Conditional Tag Removal Workflow Logic — This shows an automation workflow step that checks if a contact has a specific tag from Step 4, and if true, removes the “New Customer” tag from that entity. This logic helps users understand how to automatically clean up or update contact tags based on conditions in an Insightly automation sequence.

6 Conditional Tag Removal Workflow Logic
Workflow Automation Steps 7 and 8 — This shows two consecutive steps in an Insightly workflow automation: step 7 stops a job, and step 8 creates a new contact in Insightly with a “New Customer” tag. This would matter to readers learning how to automate contact creation as part of a multi-step workflow process.

7 Workflow Automation Steps 7 and 8

Slack

Slack is a messaging app for businesses. Use the recipes below as starting points for your own Slack recipes.

Recipe #1 Ticket to Slack

  • Connections: Slack
  • Trigger: A ticket has been submitted to Insightly Service.
  • Action: Post a message to Slack.

When a customer submits a ticket through Insightly Service, a message will be posted to a specific Slack channel to alert customer service agents.

Recipe logic:

  1. The recipe will be triggered when a ticket has been submitted.
  2. A message will be posted to a specified Slack channel.

Recipe #2 Won lead to Slack

  • Connections: Slack
  • Trigger: Lead status is updated to won.
  • Action: Post message in Slack.

When an Insightly user wins a lead, a message will be posted to a specific Slack channel to alert their team.

Recipe logic:

  1. The recipe will be triggered when a Lead’s status is updated to won.
  2. A message will be posted to a specified Slack channel.
Insightly to Slack Ticket Notification Automation — This image shows a two-step automated workflow where a new ticket created in Insightly Service triggers a real-time message posted to a Slack channel. This automation helps teams stay instantly informed about new support tickets without manually checking Insightly.
Insightly to Slack Win Notification Workflow — This diagram shows a two-step automation that triggers in real-time when a lead’s status is updated to “Won” in Insightly, then automatically posts a celebration message to a Slack channel. This would help readers understand how to set up an instant team notification whenever a sales lead is successfully closed.

Related to

Related articles

Powered by Zendesk