PYLO Connectors
iClosed
Connecting iClosed to PYLO, what it brings and how to tell it is working.
iClosed connects to PYLO so that:
- Every iClosed booking, reschedule and cancellation files as a call, exactly as a Calendly one does, so show rate and no-show rate work for a team on iClosed.
- A no-show marked in iClosed files as a no-show.
Connecting
iClosed connects by an API key you paste into PYLO. Open Settings, then Integrations, then iClosed.
- Ask iClosed's support (in-app chat or hello@iclosed.io) to turn webhooks on for your account, if they are not already.
- In iClosed, open Settings, then Developer, and add a webhook with the address below, for Call booked.
- Add the same address again for Call cancelled, Call rescheduled and Call outcome added.
- Book a test call on one of your iClosed events. It appears in PYLO's calls within a minute.
| You provide | Where to find it |
|---|---|
| API key | In iClosed, open Settings, then Developer, then API keys, and create a key. It starts with iclosed_. PYLO only reads with it. |
Before you start: iClosed's webhooks are in beta, on its Business and Enterprise plans, and iClosed's support turns them on for an account. Until they are on, nothing reaches PYLO.
What PYLO reads
- Calls booked on the account's events, with the contact, the host and the time
- The answers to the booking form's questions, kept on the lead
- Reschedules, cancellations with their reason, and no-shows
- The UTMs iClosed recorded for the contact
It does not read:
- Sales marked in iClosed: a close is filed by the closer's post-call form, which holds the amount and the plan
iClosed's own documentation: https://developer.iclosed.io/