Skip to main content

Zapier

All you need to know on how to connect Zapier with iClosed and about available triggers and actions

Updated over a month ago

While we're constantly working on adding more direct integrations with the tools you're using, Zapier is here to bridge the gaps.

For example, If you'd like to update your CRM, like Airtable, Salesforce or GoHighLevel, simply connect iClosed with Zapier, and make it happen.

How to connect Zapier to iClosed

Let's cover the basics first:

  1. Go to Settings → Integrations

  2. Click on "Connect Zapier"

  3. You'll be prompted to connect using your iClosed account

After connecting Zapier in iClosed Integrations, you would need to finish connection in Zapier when you start building first workflow.

  1. Navigate to Zapier and create new Zap

  2. Select iClosed app in the search bar, and select trigger

  3. connect iClosed account with Zapier - you can create more than one iClosed accounts in case you're operating in more than one

For every next workflow you'll have connected iClosed account available.

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 information and data you would like to transfer from iClosed to CRM or any database.

Contact by Status

One trigger for capturing a selected status, with a built in delay in the trigger, and option to send data immediately if the desired status is met.

Select Final Status - that you'd like to capture:

  • Potential - Primary, phone or email from the primary form page

  • Potential - Phone and Email, meaning Primary and Secondary information (where captured both)

  • Qualified - lead who filled out the form and pressed continue button, but didn't book a call

  • Disqualified - lead who filled out the form and pressed continue button, but wasn't able to book a call due to disqualification condition in your event

  • Strategy call booked - when a lead booked a call

Wait for X seconds

a built in delay, for adding time to wait for a contact to reach final status.
This means that if you add 120 seconds delay, trigger will not fire only after this time expires, and if the lead is still in the selected status.

Send Last Active Status

For overriding the "Wait for X seconds" delay added, and sending the latest status if a contact left before reaching Final Status selected.

Pro tips

If you'd like to capture leads as per their latest status on the scheduler journey, feel free to use following setup:

  • Select final status - Call booked

  • Wait for minimum 300 to 600 seconds (or 5-10 minutes) to give time for a lead to answer all questions and book a call with you

  • Select YES for Send last active status to override the delay trigger in case a lead drops off before booking a call

This way, you will easily capture lead as per their latest status and send it to your CRM or any other tool.

Data available

  • First and last name

  • Email

  • Phone number

  • Country, pulled from the phone number country code

  • Time Zone, as lead time zone

  • IP Address

  • Status - iClosed lead status

  • Joined Time

  • Created At

  • Updated At

  • Questions and answers, answered at the time when the trigger fired and sent information to Zapier

  • 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

  • Preview URL - Lead contact card URL

Potential contact

When a lead is created as potential (Filling primary or secondary questions).

This trigger will fire twice, first time when the phone number or email is entered on the first page of the form, and the second time when the email or phone number is entered on the second page of the form.

Data available

  • First and last name

  • Email

  • Phone number

  • Country, pulled from the phone number country code

  • Time Zone, as lead time zone

  • IP Address

  • Status, as iClosed lead status. In this case Potential

  • Blocked By Re-Captcha, showing if the lead was blocked potentially as a bot

  • Contact Joined

  • Created At

  • Updated At

  • Questions and answers, answered at the time when the trigger fired and sent information to Zapier

  • 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

Qualified contact

When a lead fills out the whole form and click on the "Continue" button, but for some reason, doesn't book a call.
​

This trigger will only fire if the lead entered the call booking page.

Data available

  • First and last name

  • Email

  • Phone number

  • Country, pulled from the phone number country code

  • Time Zone, as lead time zone

  • IP Address

  • Status, as iClosed lead status. In this case Qualified

  • Blocked By Re-Captcha, showing if the lead was blocked potentially as a bot

  • Contact Joined

  • Created At

  • Updated At

  • Questions and answers, all that are set on the form, including name, phone number, and email

  • 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

Disqualified contact

When a lead filled out the form, pressed on the "Continue" button, but wasn't able to book a call since he was disqualified by the criteria set in the event setup.

Data available

  • First and last name

  • Email

  • Phone number

  • Country, pulled from the phone number country code

  • Time Zone, as lead time zone

  • IP Address

  • Status, as iClosed lead status. In this case Disqualified

  • Blocked By Re-Captcha, showing if the lead was blocked potentially as a bot

  • Contact Joined

  • Created At

  • Updated At

  • Questions and answers, all that are set on the form, including name, phone number, and email

  • 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

Contact call booked

For prospects who booked a call on your scheduler (Strategy or Discovery call)

This trigger will provide more information that the previous three, that are related to the call booked information.

Data available

  • Event details:

    • Event name

    • Event kind, as if the call assigned to the closer manually or via round-and-robin

    • Event duration (meeting duration)

    • Event type, Strategy or Discovery event

    • Closer name (host)

    • Closer user email

    • Event reschedule and cancellation link

  • Call details:

    • Event UTC Start Time

    • Event UTC End time

    • Call start and end time UTC, per closer time zone

    • Call start and end time (pretty), in more readable format

    • Invitee call start and end time, per prospects time zone

    • Invitee start and end time (pretty), in more readable format

    • Call creation date, as time and date when the call was scheduled

    • Call location, referring to the meeting location

    • Call location link, the URL of the event

  • Lead information

    • Invitee first and last name

    • Invitee full name

    • Invitee email

    • Invitee text reminder number (as phone number)

    • Invitee time zone

    • Invitee creation date and time (when a lead entered information on the form)

  • Questions and answers, all that are set on the form, sorted by the order of appearance, including email, phone and lead name information

  • 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

Call rescheduled

Triggers when a call an upcoming call has been rescheduled, by a lead or by host (or any other iClosed user).

Data available

  • Event details:

    • Event name

    • Event kind, as if the call assigned to the closer manually or via round-and-robin

    • Event duration (meeting duration)

    • Event type, Strategy or Discovery event

    • Closer name (host)

    • Closer user email

    • Event reschedule and cancellation link

  • Call details:

    • Event UTC Start Time

    • Event UTC End time

    • Call start and end time UTC, per closer time zone

    • Call start and end time (pretty), in more readable format

    • Invitee call start and end time, per prospects time zone

    • Invitee start and end time (pretty), in more readable format

    • Call creation date, as time and date when the call was scheduled

    • Call location, referring to the meeting location

    • Call location link, the URL of the event

    • Call is rescheduled = yes

    • Reschedule reason, if any

    • Invitee reschedule by, showing information who initiated rescheduling, prospect or iClosed user (e.g. superadmin - user name)

  • Lead information

    • Invitee first and last name

    • Invitee full name

    • Invitee email

    • Invitee text reminder number (as phone number)

    • Invitee time zone

    • Invitee creation date and time (when a lead entered information on the form)

  • Questions and answers, all that are set on the form, sorted by the order of appearance, including email, phone and lead name information

  • 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

Call cancelled

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

Data available

  • Event details:

    • Event name

    • Event kind, as if the call assigned to the closer manually or via round-and-robin

    • Event duration (meeting duration)

    • Event type, Strategy or Discovery event

    • Closer name (host)

    • Closer user email

    • Event reschedule and cancellation link

  • Call details:

    • Event UTC Start Time

    • Event UTC End time

    • Call start and end time UTC, per closer time zone

    • Call start and end time (pretty), in more readable format

    • Invitee call start and end time, per prospects time zone

    • Invitee start and end time (pretty), in more readable format

    • Call creation date, as time and date when the call was scheduled

    • Call location, referring to the meeting location

    • Call location link, the URL of the event

    • Call is cancelled = yes

    • Call canceller name

    • Cancel reason, if any

    • Cancel time

    • Invitee reschedule by, showing information who initiated rescheduling, prospect or iClosed user (e.g. superadmin - user name)

  • Lead information

    • Invitee first and last name

    • Invitee full name

    • Invitee email

    • Invitee text reminder number (as phone number)

    • Invitee time zone

    • Invitee creation date and time (when a lead entered information on the form)

  • Questions and answers, all that are set on the form, sorted by the order of appearance, including email, phone and lead name information

  • 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

Call outcome

Triggers whenever an outcome is added after a call in iClosed.

Data available

  • Event name

  • Event duration and unit

  • Email

  • First and last name of the prospect

  • Phone number

  • Email

  • Call outcome

  • No sale reason, for no sale outcomes

  • Objection

  • Call start time

  • Notes from outcome objections or reasons, if any

  • Deal value

  • Product name

  • Deal transaction type

  • Deal created at

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

Select one of the following triggers:

  • Prospect name

  • Email

  • Phone number

  • Status

  • Secondary email

  • Secondary phone number

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

  • Blocked by Re-CAPTCHA (true or false)

  • Lead joined time or Lead created at, when the lead was created

  • Lead updated at, the time of the latest update

  • Referrer URL, the page URL from where the leads was captured (if any)

  • Lead updated at, the time when lead status changed

  • Deleted at, if it was deleted

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 used when a workflow is started (triggered) by any other tool in order to send information to iClosed.

Create contact

Option for adding contacts to iClosed from other apps, which will assign newly added prospect in Potential status by default. Available data to be transferred to iClosed:

  • First name

  • Last name

  • Email

  • Phone number

  • Tag - any information you'd like to place so you can identify such leads later

  • Event name - referred as event name in iClosed.
    But you would need to add it as plain text, that is exactly the same as the Event name in iClosed in order to be recognized and included when 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 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

  • Contact first name

  • Contact last name

  • Contact phone number

  • Order time

  • Order value

  • Product name - pull information from payment processor or add as plain text

  • Tag

Search contact

Fantastic option for looking into iClosed Global Data to check if the prospect already exists if it needs to be updated. Action will allow you to identify lead per:

  • Email or/and

  • Phone number

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

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.

Assign Setter Owner

Action for assigning a setter owner to a lead in iClosed Global Data. Precondition for using this action is to have Contact ID and User ID values:

  • Static - selecting it from the loaded results only or

  • Custom - that will require search step before assigning a user to the lead, so you can assign contacts dynamically per ID read in search step.

Create Contact Note

Action for creating note inside of the lead Contact Card. Precondition for using this action is to have Contact ID value:

  • Static - selecting it from the loaded results only or

  • Custom - that will require search contact step before adding a note, so you can assign contacts dynamically per ID read in search step.

Notes can be added in text form (static) inside the box or to be mapped with values from pervious steps.

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:

  1. 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

  2. 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 result

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.
    You will be able to map them with fields in your CRM (or that you'll create) or you can them as notes in your CRM contact card.
    ​

  • Troubleshooting

    Once you've connected your iClosed account with Zapier, run a test to map fields easier, and to see the output data.
    Go to your iClosed account booking a test call if you don't have any data yet.
    ​

  • Potential trigger
    Is the legacy trigger, and 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.
    We have introduced new trigger → Contact by Status that helps you fetch desired status without complex workflow setup.

Use cases, best practices and examples

Send new call booked from iClosed to CRM

A perfect use case, when you only want to send call without sending extra leads (Potentials, Qualified, Disqualified):

  1. Set iClosed Contact Call Booked trigger

  2. 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:

  1. The call time - when the call was supposed to take place

  2. The lead owner - team member that is hosting call with the prospect

Here's how to do it:

  1. Start new workflow with iClosed Call rescheduled trigger

  2. 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 call in iClosed.

Update CRM with call outcomes from iClosed

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

Strategy calls (sales calls)

  • Sale

  • No Sale

Discovery calls (setter calls)

  • Approved

  • Rejected

Follow the next steps to set it up:

  1. Select iClosed Call outcome added trigger

  2. Search for the contact in your CRM, since it was transferred already with Call booked trigger

  3. 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 with legacy triggers

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 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.

Important note

Potential trigger, as well as Qualified, Disqualified are legacy triggers. Feel free to use new trigger Contact By Status that is simpler and reduces number of steps you'd need to create in a Workflow.

Check out the video below on how to set up Zapier workflow.

For the reference, phone number is set on primary form page, email is set on secondary form 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:

  1. Select iClosed Qualified or Disqualified trigger

  2. Action - look into your CRM or any other app where iClosed potential trigger was sent already

  3. 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.

Example

Here's the visual presentation of both workflows.

  • iClosed Potential trigger is active and it already created contact in CRM

  • Google Sheets was used to represent CRM or any other end tool where you'd like to send Potential leads to.

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 workflow setup is very simple:

  1. Select trigger from CRM or any other tool from where you'd like to send information to iClosed

  2. 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 in Zapier field, that is exactly the same as the Event name in iClosed in order to be recognized and included.

Example

Here's the example where we wanted to create contacts that are considered as account owners in iClosed.

  • Trigger tool in our example is Intercom

Learn more about Contact cards in iClosed in this article here.

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

Here's how to set up Zapier 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.

  1. Select iClosed Contact Call booked trigger

  2. 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 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 Zapier

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:

  1. iClosed Call Cancelled or Call Rescheduled trigger

  2. Action Google Calendar Find Event

  3. 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 will be deleted or updated according to the Event ID 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 Zapier workflow 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:

  1. select any iClosed trigger from which you'd like to send data to Slack

    1. Potential Contact

    2. Qualified Contact

    3. Disqualified contact

    4. Contact call booked

    5. Lead status changed

    6. Contact detail changed

    7. Call rescheduled

    8. Call canceled or

    9. Call outcome

  2. 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

Additionally, you can add next steps to add updates into same Slack thread by searching the message and identifying Slack message ID where update should be added as thread.

How to send WhatsApp message to prospects

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

Here're the steps:

  1. 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

  2. select WhatsApp action send message

    1. Connect your WhatsApp by adding your phone number and entering PIN received

    2. Configure by selecting a template per your preference that WhatsApp provided. In this case select new message, but you can choose other as well:

      1. New lead

      2. Payment confirmation

      3. New order

      4. Shipping confirmation

      5. Calendar reminder

Kindly note that the lead will receive notification from Zapier as shown on the screenshot above, which is per Meta requirements.

Prospect will have the option to reply to you by clicking on the number.

Additional customization is not possible due to Meta configuration.

Learn more about how iClosed SMS notification 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 Zapier, 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.

Related Articles
HubSpot
Make
Contacts Data Columns
Contact Cards
Slack
Did this answer your question?