As iClosed team works constantly on adding more of direct integrations with your favorite apps, with over 1900 apps and tools available, Make is a fantastic workaround for connecting CRM's and payment processor apps that we do not support at this very moment.

For example, If you'd like to update your CRM, like Airtable, Go High Level or any other Make-supported app, simply connect iClosed with Make, and make it happen.

Make integration is available with Business and Enterprise subscription plans.

How to connect Make with iClosed

Navigate to Integrations page and click on the "Connect" button to get started:

Login to Make account and click on the "Install" button
Select Organization (if you have more than one account)
And finish connection by confirming with the button "Install"

Triggers available

Triggers are used for starting a workflow with iClosed, so you could forward data to any other tool.

We have made all necessary triggers to give you full flexibility over what information and data you can transfer from iClosed to CRM or any database.

New Contact By Status

Trigger for watching potential, disqualified and qualified contacts are created in iClosed.

Potential
- When a lead filled out primary or secondary questions and didn't press "Continue" button on the form
- Only trigger that fires twice, first time when phone number or email is entered on primary page and second time when email or phone number is entered on second page.
Qualified
- When a lead filled out the whole form and pressed the "Continue" button, but for some reason didn't book a call
Disqualified
- When a lead filled out the whole form and pressed the "Continue" button, but wasn't able to book a call due to disqualification criteria set in Event setup.

Data available

General information

First Name
Last Name
Email
Phone Number
Secondary Email
Secondary Phone Number
Country - per phone country code
Time zone
IP address
Status - POTENTIAL, DISQUALIFIED or QUALIFIED
Blocked by re-CAPTCHA (true or false)
Joined time - time and date when lead interacted with the scheduler
Created at - Time and date when lead was originally created
Updated at - Time and date when the lead was updated

Tracking - UTM's

Collected from cookie - if any

first_utm_term
first_utm_source
first_utm_medium
first_utm_content
first_utm_campaign

Collected from page - if any

utm_term
utm_source
utm_medium
utm_content
utm_campaign

With Key's and Values

Questions and answers

If any, depending of the lead status and if the lead filled out any answer on the form
Full name will be included

Event

Name - as the Event name
Color - in HEX code
Link prefix - from the Event name
Event type - Strategy or Discovery event

Referrer URL embed

Complete booking page URL

Contact call booked

Triggers when a new call is created in iClosed.

Data available

Event type

Kind - as how the event was assigned to closer (manually or via round and robin)
Slug - part of the event name from the URL
Name - as event name
Type - Strategy or Discovery event
Duration - in minutes
owner type - always closer

Event

Closer name
Closer time zone
Closer email
Assigned to - user name
Extended assigned to - Closer name, email and is the closer primary (True or False)
UTC start time and end time - used when you have closers with multiple time zones set in availability, so you can easily convert them to desired time zone
Start and end time - per closer time zone
Start and end time pretty - time per closer time zone with date and day included
Invitee start and end time - per invitee time zone
Invitee start and end time pretty - time per invitee time zone with date and day included
Created at - date and time when call was created
Location - referred as meeting location
Event link - referred as event URL
Type - referred as event type, Strategy or Discovery event type
Reschedule link
Cancel link
Old and New event - available for rescheduled calls only

Invitee

First and last name
Name - as full invitee name
Email
Text reminder number - referred as invitee phone number
Time zone
Created at - date and time when the lead was created
Is reschedule - true or false
Reschedule reason and Reschedule by
Cancel details - if any

Questions and answers

Sorted by the order of appearance on the form, and separated as each question and answer as a separate payload.

Questions and responses

Sorted by the order of appearance on the form, with all questions and answers in one payload.

Tracking - UTM's

Collected from cookie - if any

first_utm_term
first_utm_source
first_utm_medium
first_utm_content
first_utm_campaign

Collected from page - if any

utm_term
utm_source
utm_medium
utm_content
utm_campaign

With Key's and Values

Attendees

Providing all information about all guests of the event:

Invitee email, name and meeting location
Host email
Response status

Rescheduled call

Triggers when an upcoming call is rescheduled by a host or invitee.

Data available

Event type

Kind - as how the event was assigned to closer (manually or via round and robin)
Slug - part of the event name from the URL
Name - as event name
Type - Strategy or Discovery event
Duration - in minutes
owner type - always closer

Event

Closer name
Closer time zone
Closer email
Assigned to - user name
Extended assigned to - Closer name, email and is the closer primary (True or False)
Old start time - as the date and time of the previous call
UTC start time and end time - used when you have closers with multiple time zones set in availability, so you can easily convert them to desired time zone
Start and end time - per closer time zone
Start and end time pretty - time per closer time zone with date and day included
Invitee start and end time - per invitee time zone
Invitee start and end time pretty - time per invitee time zone with date and day included
Created at - date and time when call was created
Location - URL of the meeting location
Event link - referred as event URL
Cancelled - False
Canceler name - Always empty
Cancel reason - Always empty
Cancelled at - Always empty
Type - referred as event type, Strategy or Discovery event type
Reschedule link
Cancel link
Old event - as previous event
New event - as newly scheduled event

Invitee

First and last name
Name - as full invitee name
Email
Text reminder number - referred as invitee phone number
Time zone
Created at - date and time when the lead was created
Is reschedule - True
Reschedule reason - if any
Reschedule by - lead or iClosed user name who rescheduled a call
Cancelled - always False
Canceler name - Always empty
Cancel reason - Always empty
Cancelled at - Always empty

Questions and answers

Sorted by the order of appearance on the form, and separated as each question and answer as a separate payload.

Questions and responses

Sorted by the order of appearance on the form, with all questions and answers in one payload.

Tracking - UTM's

Collected from cookie - if any

first_utm_term
first_utm_source
first_utm_medium
first_utm_content
first_utm_campaign

Collected from page - if any

utm_term
utm_source
utm_medium
utm_content
utm_campaign

With Key's and Values

Attendees

Providing all information about all guests of the event:

Invitee email, name and meeting location
Host email
Response status

Cancelled call

Triggers whenever a call is canceled by invitee, host, or super admin (sales manager).

Data available

Event type

Kind - as how the event was assigned to closer (manually or via round and robin)
Slug - part of the event name from the URL
Name - as event name
Type - Strategy or Discovery event
Duration - in minutes
owner type - always closer

Event

Closer name
Closer time zone
Closer email
Assigned to - user name
Extended assigned to - Closer name, email and is the closer primary (True or False)
UTC start time and end time - used when you have closers with multiple time zones set in availability, so you can easily convert them to desired time zone
Start and end time - per closer time zone
Start and end time pretty - time per closer time zone with date and day included
Invitee start and end time - per invitee time zone
Invitee start and end time pretty - time per invitee time zone with date and day included
Created at - date and time when call was created
Location - referred as meeting location. It will show as plain text information
Event link - referred as event URL
Cancelled - True
Canceler name - Name of the person who cancelled the call
Cancel reason - Notes if any, provided by lead or iClosed user
Cancelled at - date and time when the call was cancelled
Type - referred as event type, Strategy or Discovery event type
Reschedule link - always empty
Cancel link - always empty

Invitee

First and last name
Name - as full invitee name
Email
Text reminder number - referred as invitee phone number
Time zone
Created at - date and time when the lead was created
Is reschedule - always false
Reschedule reason - always empty
Cancelled - referred as was the call cancelled by invitee (true or false)
Canceler name - Name of the person who cancelled the call
Cancel reason - Notes if any, provided by lead or iClosed user
Cancelled at - date and time when the call was cancelled

Questions and answers

Sorted by the order of appearance on the form, and separated as each question and answer as a separate payload.

Questions and responses

Sorted by the order of appearance on the form, with all questions and answers in one payload.

Tracking - UTM's

Collected from cookie - if any

first_utm_term
first_utm_source
first_utm_medium
first_utm_content
first_utm_campaign

Collected from page - if any

utm_term
utm_source
utm_medium
utm_content
utm_campaign

With Key's and Values

Attendees

will always remain empty

Call outcome

Triggers when a call outcome is added to Strategy or Discovery call.

Data available

General information

Event name
Event type
Closer name
Event duration
Event duration unit
Email
First and Last name
Phone number
Closer email
Call outcome
Objection
Start time
Notes
Deal value
Product name

Deal and Product details

Value
Currency
Time
Recurring - True or False
Transaction type - Won or Deposit
Created at - date and time when the deal was created
Updated at - date and time when the deal was updated
Deleted at - always empty
Name - as the Product name of the deal

Setting Outcome

Triggers when outcome (Approved or Rejected) is added in Global Data - Appointment Settings.

Data available

Outcome, as Setting outcome (Approved or Rejected)
Claim status (No Call if rejected, Scheduled if approved)
Contact ID
First and last name of the prospect
Email
Phone number
Contact status
Contact created at
User ID - user who added outcome
User email
User First and Last name
User phone number

Lead status changed

Triggers whenever a lead status changes from inside iClosed - Global Data.

Data available

First and last name
Email
Phone number
Secondary email (if any)
Secondary phone number (if any)
Country, pulled from the phone number country code
Time Zone, as lead time zone
IP Address
Lead status, as per latest change
Blocked by Re-CAPTCHA (true or false)
Lead joined time or Lead created time, when the lead was created
Lead updated at, the time when lead status changed
Questions and answers, answered at the time when the trigger fired and sent information to Zapier (if any, depending of the lead stage)
Event details:
- event name
- event color in HEX code
- event link prefix
- event type (Strategy or Discovery call)
Tracking UTM's if any, in cookies or set on the page, such as:
- Tracking Utm Term
- Tracking Utm Source
- Tracking Utm Medium
- Tracking Utm Content
- Tracking Utm Campaign
- Tracking Utm Keys and values
Referrer URL Embed, the page URL (if any)

Contact Updated

Triggers whenever a detail is updated in the prospect contact card, such as:

Prospect name
Email or phone number change
Adding secondary email and phone number
and even status update

Data available

First and Last name
Email
Phone number
Secondary email - if added
Secondary phone number - if added
Country - per phone number country code
Time zone
IP Address
Status - referred as lead status (Potential, Qualified, Disqualified, Discovery or Strategy call booked)
Blocked by re-CAPTCHA - True or False
Joined or Created time - date and time when lead was created
Updated at - date and time of the latest contact update
Deleted at - date and time of a contact was deleted
Referrer URL embed - Complete booking page URL

Contact Note Added

Triggers whenever a note is added to the lead Contact Card.

Data available

Note - as the note text
Type - as the type of the note (e.g. Contact card, Outcome, ...)
First and last name
Email
Phone number
Secondary email
Secondary phone number
Contact preview ID - URL suffix of lead contact card from Global Data
Note in HTML

Contact Setter Owner assigned

Triggers whenever a new Setter is assigned in Global Data.

Data available

Outcome, as Setting outcome (Approved or Rejected)
Claim status (No Call if rejected, Scheduled if approved)
Contact ID
First and last name of the prospect
Email
Phone number
Contact status
Contact created at
User ID - user who added outcome
User email
User First and Last name
User phone number

Contact Custom Field answered

Triggers whenever a custom field answer is selected or added. The trigger has a multi-select dropdown for choosing the custom field.

Multi-select dropdown will fetch custom fields on run-time from the app, when custom fields are answered/updated.

Data available

Custom Field Event ID
Custom Field name
Input type, as contact custom field type (e.g. Radio Button, Checkbox, ...)
Options as all answer options available for drop down fields
Answer
Contact ID
Created At
Updated At
Deleted At
Joined time
First and Last name
Email
Phone Number
Preview ID - suffix of contact card URL from Global Data
Secondary email
Secondary phone number
Status as latest lead status from iClosed
Referrer URL

Transaction synced

Triggers whenever a transaction is synced with a deal.

Data available

Event Name
Event ID
Event Duration
Call start time
Contact ID
Email
First and last name
Phone number
Closer email
Call outcome -SALE
Objection
Outcome note
Deal value
Product name
Transaction type
Deal created at
Transaction source
Transaction lead email
Transaction lead name
Transaction lead phone number
Transaction created at

Actions available

Actions are for cases when a workflow is started (triggered) by any tool, in order to forward information collected by a trigger to iClosed.

Create a new contact

For adding contacts to iClosed from other apps, that will set the newly added prospect in the Potential status by default. Available data that can be transferred to iClosed:

Email - mandatory field
Phone number
First name
Last name
Tag - any information you'd like to place so you can identify such leads later
Event - referred as event name in iClosed.
But you would need to add it as plain text in Make field, that is exactly the same as the Event name in iClosed in order to be recognized and included when the contact is created.

Update Contact

Action for updating existing contact in iClosed. Precondition for using this action is to choose Contact ID value:

Static - selecting it from the loaded results that will update selected contact ID only or
Custom - that will require Search Contact in iClosed step before update contact, so you can update contacts dynamically per read ID in search step.

Once the Contact ID is defined, you will be able to update following lead information:

Phone number
First name
Last name
Secondary email
Secondary phone number
Email

Create new Transaction

Action for creating transactions in iClosed (collecting payments from any payment processor) that you can use for connecting deals when adding "Sale" outcome.

Available data to be transferred to iClosed:

Contact email - mandatory
Contact first name
Contact last name
Contact phone number
Order time
Order value - mandatory
Product name - pull information from payment processor or add as plain text
Tag

Search contact

Excellent option for looking into iClosed Global Data to check if the prospect already exists, before updating. Action will allow you to identify lead per:

Email - mandatory
Phone number

Data available

Email
First name
Last name
Email address
Phone number
Secondary email
Secondary phone number
Event name
Event type - Discovery or Strategy event type
Country
Time zone
IP address
Status
Blocked by re-CAPTCHA - True or False
Joined and created time - date and time when the lead was created
Updated at
Deleted at
Referrer URL

Add Call Outcome

Action for adding call outcomes from any other tool to iClosed. Precondition for using this action is to choose Event Call ID value:

Static - selecting it from the loaded results that will add outcome to call per selected Event Call ID only or
Custom - that will require Search Event in iClosed step before adding call outcome, so you can update them dynamically per read ID in search step.

Once the Event Call ID is defined, you will be able to update following lead information:

Won (Sale):

Objection
Product
Deal Value
Transaction type (Won or Deposit)
Notes

No Sale

No Sale Reason - but Follow up scheduled will add outcome only, without possibility to book additional follow up call.
Objection - will be mandatory field, and needs to be mapped no matter if No Show, or Not interested reasons are not requiring objections in iClosed.
Notes

Cancel Event Call

Action for adding call outcomes from any other tool to iClosed. Precondition for using this action is to choose Event Call ID value:

Static - selecting it from the loaded results that will cancel call per selected Event Call ID only or
Custom - that will require Search Event in iClosed step before cancelling the call, so you can update dynamically per read ID in search step.

Additional option is to add cancel reason, by entering text in the field, or mapping value from previous step.

Update Setter owner

Action for assigning Setter owners to leads automatically in Global Data - Appointment Setting. All you need to do is to map both mandatory fields:

Invitee email address
Setter email address

Create a new contact note

Perfect for adding notes or comments from external tools into iClosed contact note.

Email - mandatory field, for mapping of email of the contact
Note - mandatory field for imputing all information you'd like to forward from CRM

Create Custom Contact Field

For creating new custom field in Global Data.

Name
Input Type with all available field format types in iClosed
- Number
- Text
- Checkbox
- Radio Button
- Date
- Text field
- User
- URL
Depending of the field type selected, additional field will be available "Options", which are basically answers for the custom contact field question.

Search Custom Field

Option for looking into iClosed Global Data to check if the Custom Contact field already exists or not. Action will allow you to identify lead per:

Field name
Field type (event or contact field)
Input type, per field format types from iClosed

Additionally, you will be able to select should the workflow stop or continue depending "if no search results are found":

Mark successful and run steps that use search results or
Mark safely halted and skip steps that use search result

Answer Custom Fields

Action for updating Contact custom fields in Global Data for a specific lead. Precondition for using this action is to have Contact ID and Custom field ID value:

Static - selecting it from the loaded results only or
Custom - that will require search contact and search custom field so you can update contact fields dynamically

Search Event Call

Option for searching calls in iClosed. Action will require Contact ID as a unique identifier, which you'd need to search out before searching event call. Additional filtering options for narrowing down the search are:

Date of the call
Type of event, Strategy or Discovery
Closer ID, static by selecting a specific user from the list, or custom, which would require a search User step

Additionally, you will be able to select should the workflow stop or continue depending "if no search results are found":

Mark successful and run steps that use search results or
Mark safely halted and skip steps that use search result

Search Users

Option for searching iClosed User:

Email of the user
Name of the user

There are two additional options:

Select should the workflow stop or continue depending "if no search results are found":
1. Mark successful and run steps that use search results or
2. Mark safely halted and skip steps that use search result
If multiple search results are found:
1. Only use first search result (default)
2. Group all search results as line-items
3. Mark "safely halted" and skip steps that use search results

Search Transactions

Option for looking into iClosed Transactions to check if the transaction was picked by iClosed or not. Search options available are:

Name, as the name of the lead
Synced, as transaction status in iClosed, True - connected to a deal or False
Email of the lead
Phone number
Source of the transaction
Value of the transaction

Additionally, you will be able to select should the workflow stop or continue depending "if no search results are found":

Mark successful and run steps that use search results or
Mark safely halted and skip steps that use search resuls

Get Custom Fields

API call configuration could be useful for fetching data, creating and updating records, or deleting from other tools with specified API endpoint path. Available HTTP methods are:

GET: For retrieving data
POST: For submitting or creating data
PUT: For updating or replacing data
PATCH: For partial updates to data
DELETE: For deleting data

Pro tips

Before moving forward with the integration and mapping of the fields, please double check available fields in the tool where you'd want to send data to:

Create custom field in your CRM for Call time if needed
this will help you update this field when a call is rescheduled.
Invitee questions (form questions)
will appear in order as they are sorted on the form, showing both question titles and answers as values. Additionally, you will be able to choose from two format types:
- Question and answers - every question and answer as separate data output
- Question and responses - All questions and answers shown as plain text in one output
- This gives you additional options to decide how you'd like to map answers in your CRM (if needed create custom fields) or add them as notes in your CRM contact card.
Troubleshooting
Once you've connected your iClosed account with Make, run a test to map fields easier and to see the output data.
- Create scenario and click on the "Run" button
- Go to your iClosed account and trigger data required to test in Make

Use cases, best practices and examples

How to create a new scenario in Make

Click on the "Create new scenario" button
Search out for iClosed app and select the trigger and create a webhook
Create connection
If you're doing this for the first time enter iClosed login credentials and press "Save" button
After the connection is established, select iClosed account from where you'd like to generate a trigger (if more than one)
Click on the "Run Once" button in the bottom left on your screen to start testing
Navigate back to iClosed app to generate the trigger for the webhook you've created and according to the trigger selected (e.g. Call booked = book a test call)
Once you fire the trigger in iClosed, data will appear in Make

Send new call booked from iClosed to CRM

A perfect use case, when you only want to send call without sending the extras leads

(Potentials, Qualified, Disqualified):

Create a scenario and select iClosed Contact Call Booked trigger
Update contact:
1. Assuming that you've set at least potential trigger that will create contact in your CRM
2. If not, set Search for contact in CRM as step #2 and split workflow in two paths:
  1. One when contact is found = next step Update contact
  2. Other when contact is not found = next step Create contact

Additionally, you can add another workflow for adding call outcomes in iClosed and transferring them to your CRM.

Learn more about how to create your first event.

Update call time and lead owner in case of rescheduling

If a call is rescheduled by host or an invitee, two important data needs to be updated in your CRM:

The call time - when the call was supposed to take place
The lead owner - team member that is hosting call with the prospect

Here's how to do it:

Start new scenario with iClosed Call rescheduled trigger
Update contact
1. Assuming that you've set at least New call booked trigger that will create new call for your contact in CRM - Update Closer name or/and new Call Start Time
2. If not, set Search for contact in CRM as step #2 and split workflow in two paths:
  1. One when contact is found = next step Update contact
  2. Other when contact is not found = next step Create contact

Learn more on how to reschedule or cancel a call.

Update CRM with call outcomes from iClosed

Your sales representatives need to add Call Outcomes after each and every call to provide you with feedback on their sales activity. As iClosed provides two types of calls, each call type will have two types of outcomes:

Strategy calls (sales calls)

Sale
No Sale

Discovery calls (setter calls)

Approved
Rejected

Follow the next steps to set it up:

Select iClosed Call outcome added trigger
Search for the contact in your CRM, since it was transferred already with Call booked trigger
Map with the outcome fields in your CRM
In case you don't have such field in your CRM, create it as custom field first.
Make sure to create fields for call outcomes, and outcome reasons, or add such information in notes.

Learn more about iClosed Call outcomes here.

Sending Potential, Qualified or Disqualified contacts to your CRM

Building the workflow for Potential leads

A lead becomes potential as soon as they enter phone number or email on the first page of the scheduler form, and will remain in such status until it clicks on the "Continue" button and access booking page.

This is the only trigger that will fire twice! First time when email or phone number is collected on the primary form page, and the second time when phone number or email is filled out on the secondary form page.

Here's the best practice on how to set up this scenario to avoid duplicate entries:

Start the scenario with iClosed Potential trigger
Create Make Router and split flow into two paths:
Path A (data is entered on primary page):
1. Next step (action) - Create contact in your CRM
2. Add filter Continue IF = prospect email "Does not exist"
3. This will prevent second trigger to add new contact in your CRM
Path B (data is entered on the secondary page):
1. Next step (action) - Search contact in your CRM
2. Add filter Continue IF = prospect email "Exists"
3. Next step (action) - Update contact in your CRM
4. Add filter Continue IF = Email field in your CRM "Doesn't equal" prospect email
Build additional actions per your preference.

With this setup you will prevent Potential contact to be created (sent) twice, due to double triggering when lead enters both Phone Number and Email.

Example

Here's the visual presentation of the workflow.

Phone number is set on primary form page
Email is set on secondary form page
Google Sheets was used to represent CRM or any other end tool where you'd like to send Potential leads to

Path A (data is entered on primary page) - Create new contact from information collected on the primary page

Path B (data is entered on primary page) - Data collected on the secondary page

Path B1 - Search contact in your CRM per data collected on primary page

Path B2 - Update CRM with additional information from secondary page

Building the workflow for Qualified or Disqualified leads

A Qualified and Disqualified leads have one thing in common. Both are applied to leads who filled out the whole form, clicked on the "Continue" button, accessed the booking page and they didn't book a call.

That being said, the only difference between the two is if they were able to book a call or not:

Qualified didn't book the call for any reason
Disqualified were not able to book a call since they were disqualified by criteria you've set in the event setup

Here's the best way to set up the workflow, having in mind that you've probably created this contact in your CRM by using iClosed potential trigger:

Select iClosed Qualified or Disqualified trigger
Action - look into your CRM or any other app where iClosed potential trigger was sent previously
Action - update your CRM or any other app where iClosed potential trigger was sent already with all available information per your preference, per search results in step number 2 - look into your CRM

In case you haven't set iClosed potential trigger, and you're starting with Qualified or Disqualified trigger, set action #2 to be Create contact in CRM or send information in any other tool per your preference.

Learn more about iClosed Lead Statuses here.

Importing contacts from CRM or any other tool to iClosed

This option allows you to add leads (contacts) from a CRM or any other tool to iClosed. The scenario setup is very simple:

Select trigger from CRM or any other tool from where you'd like to send information to iClosed
Use iClosed Create Contact action

Following data is available to be transferred:

First name
Last name
Email
Phone number
Tag - any information you'd like to place so you can identify such leads later
Event name - add it as plain text, that is exactly the same as the Event name in iClosed in order to be recognized and included

Learn more about iClosed Contact cards here.

Assigning Setters from CRM to iClosed - Appointment setting

How to set it up?

Before we proceed, kindly note that Setter assigning is available for Potential, Qualified, and Disqualified leads, that haven't booked a call with your team.

Automate prospect ownership in several simple steps:

Set "Watch New Contacts" trigger first
Add new action "Update Setter Owner" and set with which setter you'd like to update selected leads

Leads will be assigned automatically as "Current Setter Owner"

Build additional actions if needed to notify Setters (e.g. email).

Can I randomly assign setters?

Round and robin options are not available for this automation

Alternatively, you can assign all leads to the sales manager who will be doing reassigning from iClosed per your process or to leave all empty and assign in bulk manually from iClosed.

Learn more about assigning leads in bulk here.

What are the options for assigning different setters to leads?

There are two scenarios available for assigning setters automatically, but it depends on your internal process. Here's how:

When a team member is managing leads in CRM first

Create Make scenario with workflow starting with lead ownership in CRM
set iClosed action for looking into lead
Use iClosed action for assigning setters to the same lead as it was assigned in CRM

With this setup you will ensure all leads that are assigned to owner in CRM are automatically assigned to the same user in iClosed.

When team members are managing leads in iClosed first

There are two available options depending on how you'd like to set up automation:

Assigning setters per lead status
(e.g. Potential = Setter 1, disqualified/qualified = setter 2)
1. Trigger would be iClosed new contact created - e.g. Potential
2. Assign to specific setter
3. Create additional scenarios for other lead statuses - e.g. Qualified/Disqualified and assign to specific setter
Assigning leads per event
(e.g. Event 1 = Setter 1, Event 2 = Setter 2)
1. Trigger would be iClosed new contact created
2. Split the workflow into paths per event name
3. Assign to specific setter per event name
4. Create additional scenarios for other lead statuses - e.g. Qualified/Disqualified and assign to specific setter

Learn more about iClosed Global Data Appointment Setting feature.

How to add note from CRM or any other tool to iClosed contact card

Follow the next steps:

Create scenario with the app trigger from where you'd like to pull information to be sent to iClosed Contact card notes.
Set iClosed action "Create a New Contact Note"

The note will be added to prospect Contact Card, visible in the "Notes" section and the "Contact Card Journey" as well.

Learn more about how to add notes in iClosed Contact Card.

Setting up iClosed events to be added and show up as "Busy" in your private (secondary) calendars

Here's how to set up Make automation in case you're running more than one business, or for any other reason you need to book slots in different calendars, that must show as "Busy" in the secondary calendar.

Select iClosed Contact Call booked trigger
Choose Google Calendar action Create detailed Event
1. Make sure to map all fields you'd like to have in secondary calendar
2. Even though Google should add these event in "Busy" status by default, to be safe please set "Busy" in Show me as Free or Busy option

Once you're done, your event will appear as added event in "Busy" status in the secondary calendar as well, not just as shared from the other calendar.

Pro tips

You can use the same steps in reversed way in case you'd need to send out events from your alternate calendar to the primary calendar.

But, kindly note that iClosed already provides option for checking against conflicts in secondary calendars in the AI Scheduler → Calendar Connections page.

Additionally, you can always troubleshoot Availability to double check which Google Calendar events iClosed sees as taken slots in the AI Scheduler → Availability → Launch troubleshooter.

Learn more

Updating secondary calendar via Make

To receive updates from iClosed about cancelled and rescheduled events, you'd need to set up additional zaps for cancelled calls and rescheduled calls. Simply select:

iClosed Call Cancelled or Call Rescheduled trigger
Action Google Calendar Find Event
For cancelled calls select Google Calendar Delete event action and for rescheduled calls, select Google Calendar Update Event
1. In both cases select event - Custom value and select Event ID from Google Find Event in step #2

Test it out and the event per ID will be deleted or updated from Google Calendar.

Learn more about how to cancel or reschedule call in iClosed.

How to send iClosed information as Slack notification

Pro tips

iClosed has direct Slack integration that is available with all subscription plans. But, in case you'd like to connect one iClosed account with more than one Slack workspace, you do that by building a Make scenario as per instructions below.

iClosed Potential is the only trigger that requires additional setup since it fires the trigger twice (learn more about it here and how to prevent duplicates).

Here're the steps:

select any iClosed trigger from which you'd like to send data to Slack
select Slack action per your preference (e.g. send message to channel, direct message, etc...), configure which details you'd like to send over and you're done ( See all available Slack triggers and actions here).

How to send WhatsApp message to prospects

Kindly note that Make is allowing connection with WhatsApp business accounts only ( see all information about WhatsApp triggers and actions here).

But this kind of a setup is applicable to any text message provider who has actions available in Make for sending out messages.

Here're the steps:

select any iClosed trigger from which you'd like to send data via WhatsApp.
Usually it's Contact call booked for sending confirmation message to the lead
select WhatsApp action send message
1. Connect your WhatsApp by entering API key from your business account
2. Configure message

Learn more about how iClosed SMS notifications work.

As per shown above, iClosed provides triggers for almost every scenario you may need.

But in case you have an improvement proposal what we should include in Make, or if we need to introduce additional information to the existing triggers and actions, feel free to let us know by contacting our Customer Support team via chat button below.