Escalated support gets a room, not a reminder
When a student needs a real conversation, remove the setup delay.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a Meet
Why this helps
Urgent support issues linger because creating a meeting is separate from recognizing the escalation.
- Respond faster to serious student issues
- Separate urgent conversations from inbox noise
- Create a consistent escalation path
Setup
Build it in a few focused steps.
- 1Connect Heights Platform and Google Meet to Notis once in the portal.
- 2Ask Notis to create a Google Meet space whenever a Heights support escalation webhook arrives, including the issue summary in the meeting context.
- 3Pick an incoming webhook as the trigger and choose your run-report channel.
- 4Test with one genuine escalation or a safe test payload.
Questions about this workflow
What qualifies as an escalation?
Your Heights-connected support process decides when to send the webhook to Notis.
Can this replace written support?
No. It adds a focused meeting space when a written issue needs live attention.
When this happens · Trigger
Do this · Action
Creates a Meet space with join details; it is not linked to a calendar event.
Conditions and details
The new space can have configured access controls, moderation, recording, or transcription settings. It is not attached to a calendar event; linking it requires a separate calendar action. Creating a space requires authorization that includes the meetings.space.created permission. Rapid calls can be throttled; exponential backoff may be needed. The result includes the meeting link, meeting code, and space reference for later lookups.
Supported Triggers and Actions
Notis builds workflows that link Heights Platform to Google Meet. A trigger fires from one place; an action lands in another.
Heights Platform triggers
Google Meet actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Google Meet Space
Creates a Meet space with join details; it is not linked to a calendar event.
Conditions and details
The new space can have configured access controls, moderation, recording, or transcription settings. It is not attached to a calendar event; linking it requires a separate calendar action. Creating a space requires authorization that includes the meetings.space.created permission. Rapid calls can be throttled; exponential backoff may be needed. The result includes the meeting link, meeting code, and space reference for later lookups.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Batch Update Google Meet Members
Update 1 to 500 members in one Meet space; without an update mask, unset fields are cleared.
End active conference
Ends the conference and immediately drops participants if it is active in the specified space; confirm first.
Get Meet details
Retrieve details about a meeting space.
Get conference record by name
Retrieves details about a specific conference record.
Create Member
Add a member to a Meet space, optionally granting co-host status that lets them join without knocking.
Get Participant Session
Retrieve details about a participant’s session in a conference.
Delete Google Meet Space Member
Remove a member’s role assignment from a Meet space; this does not remove them from an active conference.
Connect any two apps with Notis in the middle.
Heights Platform and Google Meet, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Google Meet.