Upgrade to ApiMonster from Zapier, Make, and other no-code services. We have optimal tariffs and a unique
Live chat support for your projects DS
CLUB.
Integration Calendly and My class (My class)
Connection in 5 minutes, 30 days on tests, try.
Accepted webhooks
Done actions
New clients
Free Turnkey setting, Instructions.
What data can be transmitted from: from_Service to: to_Service
Important:
Please note that the presence of events and actions between the two services does not guarantee a solution
your task - the available events and actions may not connect with each other in the way you need.
If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.
If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.
Events c Calendly
Click on the name of the event to see the available fields.
API documentation — No.
Description
Not
Available fields
| Id | Name |
|---|---|
created_at
|
The date when the event was created. Example: 2020-01-02T03:04:05.678123Z |
created_by
|
The user who created the event |
payload.uri
|
Link to the invited person |
payload.email
|
Email of the invited person |
payload.first_name
|
Name of the invited person |
payload.last_name
|
Last name of the invited person |
payload.name
|
Name of the invited person |
payload.status
|
Event status: active,cancelled |
payload.questions_and_answers
|
Questions and answers of the invited |
payload.timezone
|
The time zone of the invitee |
payload.event
|
Link to the event |
payload.created_at
|
The date the event was created. Example: 2020-01-02T03:04:05.678123Z |
payload.updated_at
|
The date of the event update. Example: 2020-01-02T03:04:05.678123Z |
payload.tracking.utm_campaign
|
utm_campaign |
payload.tracking.utm_source
|
utm_source |
payload.tracking.utm_medium
|
utm_medium |
payload.tracking.utm_content
|
utm_content |
payload.tracking.utm_term
|
utm_term |
payload.tracking.salesforce_uuid
|
UUID Salesforce |
payload.text_reminder_number
|
The number for sending SMS reminders |
payload.rescheduled
|
Event postponement flag (true/false) |
payload.old_invitee
|
Link to the old invitation, if there was a transfer |
payload.new_invitee
|
A link to the new invitation, if there was a transfer |
payload.cancel_url
|
A link to cancel the event for the invited person |
payload.reschedule_url
|
A link to reschedule the event for the invitee |
payload.routing_form_submission
|
Link to the completed form |
payload.cancellation.canceled_by
|
Full name of the person who canceled the event |
payload.cancellation.reason
|
The reason for the cancellation of the event |
payload.cancellation.canceler_type
|
Type of canceller: host - creator, invitee - invited |
payload.payment.external_id
|
Payment ID |
payload.payment.provider
|
Payment Provider |
payload.payment.amount
|
Payment amount |
payload.payment.currency
|
Payment currency |
payload.payment.terms
|
Payment terms |
payload.payment.successful
|
Payment success flag: true, false |
payload.no_show.uri
|
The URL for the non-appearance of the invited person |
payload.no_show.created_at
|
The date when the no-show was created. Example: 2019-01-02T03:04:05.678123Z |
payload.reconfirmation.created_at
|
The date when the re-confirmation was created. Example: 2019-01-02T03:04:05.678123Z |
payload.reconfirmation.confirmed_at
|
The date of the re-confirmation. Example: 2019-01-02T03:04:05.678123Z |
payload.scheduled_event.uri
|
URL to the scheduled event |
payload.scheduled_event.name
|
Name of the planned event |
payload.scheduled_event.status
|
The status of the planned event: active - active, cancelled - canceled |
payload.scheduled_event.start_time
|
The start time of the scheduled event is in UTC. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.end_time
|
The end time of the scheduled event is in UTC. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.event_type
|
Event type of the planned event |
payload.scheduled_event.location.type
|
The type of place of the planned event |
payload.scheduled_event.location.location
|
Address of the place of the planned event |
payload.scheduled_event.invitees_counter.total
|
The total number of invited to the planned event |
payload.scheduled_event.invitees_counter.active
|
The number of active invitees of the planned event |
payload.scheduled_event.invitees_counter.limit
|
The limit of the number of invited to the planned event |
payload.scheduled_event.created_at
|
The date the planned event was created. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.updated_at
|
The date of the scheduled event update. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.event_memberships
|
List of participants of the planned event |
payload.scheduled_event.event_guests
|
The list of guests of the planned event |
payload.scheduled_event.cancellation.canceled_by
|
Full name of the person who canceled the event |
payload.scheduled_event.cancellation.reason
|
The reason for the cancellation of the event |
payload.scheduled_event.cancellation.canceler_type
|
Type of canceller: host - creator, invitee - invited |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
created_at
|
The date when the event was created. Example: 2020-01-02T03:04:05.678123Z |
created_by
|
The user who created the event |
payload.uri
|
Link to the invited person |
payload.email
|
Email of the invited person |
payload.first_name
|
Name of the invited person |
payload.last_name
|
Last name of the invited person |
payload.name
|
Name of the invited person |
payload.status
|
Event status: active,cancelled |
payload.questions_and_answers
|
Questions and answers of the invited |
payload.timezone
|
The time zone of the invitee |
payload.event
|
Link to the event |
payload.created_at
|
The date the event was created. Example: 2020-01-02T03:04:05.678123Z |
payload.updated_at
|
The date of the event update. Example: 2020-01-02T03:04:05.678123Z |
payload.tracking.utm_campaign
|
utm_campaign |
payload.tracking.utm_source
|
utm_source |
payload.tracking.utm_medium
|
utm_medium |
payload.tracking.utm_content
|
utm_content |
payload.tracking.utm_term
|
utm_term |
payload.tracking.salesforce_uuid
|
UUID Salesforce |
payload.text_reminder_number
|
The number for sending SMS reminders |
payload.rescheduled
|
Event postponement flag (true/false) |
payload.old_invitee
|
Link to the old invitation, if there was a transfer |
payload.new_invitee
|
A link to the new invitation, if there was a transfer |
payload.cancel_url
|
A link to cancel the event for the invited person |
payload.reschedule_url
|
A link to reschedule the event for the invitee |
payload.routing_form_submission
|
Link to the completed form |
payload.cancellation.canceled_by
|
Full name of the person who canceled the event |
payload.cancellation.reason
|
The reason for the cancellation of the event |
payload.cancellation.canceler_type
|
Type of canceller: host - creator, invitee - invited |
payload.payment.external_id
|
Payment ID |
payload.payment.provider
|
Payment Provider |
payload.payment.amount
|
Payment amount |
payload.payment.currency
|
Payment currency |
payload.payment.terms
|
Payment terms |
payload.payment.successful
|
Payment success flag: true, false |
payload.no_show.uri
|
The URL for the non-appearance of the invited person |
payload.no_show.created_at
|
The date when the no-show was created. Example: 2019-01-02T03:04:05.678123Z |
payload.reconfirmation.created_at
|
The date when the re-confirmation was created. Example: 2019-01-02T03:04:05.678123Z |
payload.reconfirmation.confirmed_at
|
The date of the re-confirmation. Example: 2019-01-02T03:04:05.678123Z |
payload.scheduled_event.uri
|
URL to the scheduled event |
payload.scheduled_event.name
|
Name of the planned event |
payload.scheduled_event.status
|
The status of the planned event: active - active, cancelled - canceled |
payload.scheduled_event.start_time
|
The start time of the scheduled event is in UTC. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.end_time
|
The end time of the scheduled event is in UTC. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.event_type
|
Event type of the planned event |
payload.scheduled_event.location.type
|
The type of place of the planned event |
payload.scheduled_event.location.location
|
Address of the place of the planned event |
payload.scheduled_event.invitees_counter.total
|
The total number of invited to the planned event |
payload.scheduled_event.invitees_counter.active
|
The number of active invitees of the planned event |
payload.scheduled_event.invitees_counter.limit
|
The limit of the number of invited to the planned event |
payload.scheduled_event.created_at
|
The date the planned event was created. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.updated_at
|
The date of the scheduled event update. Example 2020-01-02T03:04:05.678123Z |
payload.scheduled_event.event_memberships
|
List of participants of the planned event |
payload.scheduled_event.event_guests
|
The list of guests of the planned event |
payload.scheduled_event.cancellation.canceled_by
|
Full name of the person who canceled the event |
payload.scheduled_event.cancellation.reason
|
The reason for the cancellation of the event |
payload.scheduled_event.cancellation.canceler_type
|
Type of canceller: host - creator, invitee - invited |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
created_at
|
The date when the event was created. Example: 2020-01-02T03:04:05.678123Z |
created_by
|
The user who created the event |
payload.uri
|
Link to the completed form |
payload.routing_form
|
Link to the form associated with the event |
payload.questions_and_answers
|
Questions and answers of the invited |
payload.tracking.utm_campaign
|
utm_campaign |
payload.tracking.utm_source
|
utm_source |
payload.tracking.utm_medium
|
utm_medium |
payload.tracking.utm_content
|
utm_content |
payload.tracking.utm_term
|
utm_term |
payload.tracking.salesforce_uuid
|
UUID Salesforce |
payload.result.type
|
Indicates that sending the routing form resulted in redirection to the event type booking page |
payload.result.value
|
Link to the type of event |
payload.payment.submitter
|
Link to the invitation if submitting the form leads to a planned event |
payload.payment.submitter_type
|
The type of respondent resource that submitted the form and scheduled the event |
payload.created_at
|
The date of filling out the form. Example: 2020-01-02T03:04:05.678123Z |
payload.updated_at
|
The date the form was updated. Example: 2020-01-02T03:04:05.678123Z |
+ You can add your fields that are in webhuk.
If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.
Actions in My class
Click on the name of the action to see the available fields.
API documentation — No.
Request fields
| Id | Name |
|---|---|
userId
|
User ID |
Answer fields
| Id | Name |
|---|---|
id
|
id |
name
|
name |
email
|
|
phone
|
phone |
advSourceId
|
advSourceId |
createSourceId
|
createSourceId |
stateChangedAt
|
stateChangedAt |
createdAt
|
createdAt |
updatedAt
|
updatedAt |
filials
|
filials |
responsibles
|
responsibles |
attributes
|
attributes |
joins
|
joins |
Integration setup plan Calendly with My class
| 1 | Configure the connection for: Service in Apimonster. |
| 2 | Configure Webhuk in: Service, indicating the link from Apimonster. |
| 3 | Configure the connection for: Service in Apimonster, indicating the login/password/token for access to the API. |
| 4 | Create a bunch. |
| 5 | Indicate as a data source: Service. |
| 6 | Create the required action for: to_Service, indicating in which fields: to_Service to transmit field values from: from_Service. |
| 7 | Configure filters for each step if necessary. |
| 8 | Test the bundles and make sure that they work according to the TOR. |
Or go through the full well on ApiMonster.
Check out other ApiMonster features
NoCodeStore - a store of ready-made no-code solutions
Ready-made customized bundles for popular business tasks
Whatsapp Tracker for Yandex.Metrica
Uploading conversions to Yandex.Metrica on the first message from Whatsapp
Is free
FAQ
How does the app differ from regular bundles?The application is not an alternative to bundles, but simply a preset set of bundles (template) for popular tasks to speed up setup.
Is it possible to change the logic of the created bundles?Yes. The created set of bundles can be customized according to your tasks or left unchanged if everything works as it should.
