Schedule an interview panel without the thread
A workable slot found across the panel, with invitations drafted and waiting for your approval. Built for a recruiter coordinating four calendars and a candidate.
Google Calendar
Gmail
4 steps2 integrationsRuns before each meeting
Four calendars and a day of messages. What it costs while the work is still done by hand.
- 01Finding one slot across four calendars takes a day of messages.
- 02The candidate waits while internal availability is gathered.
- 03Rescheduling one interviewer restarts the whole thing.
- Read calendars4 panelists · next 10 days
- Find slotsThu 11:00 · 2 alternates
- Draft invitescandidate and 4 panelists
- Approve, sendadd_attendees_to_event · sent
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the panel's availability.Google Calendar
- 02Find the slots that work for everyone.ModuleX
- 03Draft the invitation to the candidate and the panel.Gmail
- 04Review and approve before invitations go out.Google Calendar
The workflow is an editable graph. Reading runs freely; review and approve before invitations go out waits for your opt-in approval until you loosen it. The graph is the receipt.
A slot that works. Paste this into ModuleX chat, or hit Use this workflow.
schedule an interview panel without the thread: read the panel's availability; find the slots that work for everyone; draft the invitation to the candidate and the panel; review and approve before invitations go out. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Schedule an interview panel without the thread. A workable slot found across the panel, with invitations drafted and waiting for your approval.
- google calendar · create_event
- gmail · send_message
A workable slot found across the panel, with invitations drafted and waiting for your approval.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Brief yourself on a candidate before the callA brief covering the role, the application, and what earlier rounds already established. Built for an interviewer who opens the CV two minutes before the interview.- Prepare everything a new joiner needs on day oneA per-role onboarding checklist with real owners and dates, created before the start date. Built for an operations lead who assembles the same onboarding list every time, from memory.
Prepare an offer and send it for signatureAn offer letter produced from the approved details, checked by a person, then sent for signature. Built for whoever assembles offer letters from a template and hopes the numbers are right.
About this use case.
No. Anything sent externally waits for your approval.