↔
Meetings from Google Calendar show up in Slack on time, and Slack can book, move and answer them
The team plans in Google Calendar and talks in Slack. Without a link people miss a meeting that was moved an hour ago, the channel does not know who is busy, and booking a call means switching to the calendar and back. We connect the two so a channel gets a reminder before each meeting, changes are announced where the team already is, and a meeting can be booked or moved with a short command in Slack.
Before the organiser moves the call by an hour, the email notification drowns in the inbox and three people join at the old time.
After the change is posted in the team channel within a minute with the new time and a button to open the event.
Before the manager asks in the channel who is available on Thursday, gets five answers over two hours and books the slot that no longer works for one of them.
After one command returns the shared open slots from the calendars and books the chosen one with invitations to all five.
Before a colleague pings with an urgent question in the middle of a client call because nothing in Slack shows the person is busy.
After the status shows the meeting and its end time, so colleagues wait or ask someone else.
Before the team lead opens three calendars every morning to see what the team has today and posts a summary by hand.
After the day's agenda for the team calendar appears in the channel at the chosen time, in one message.
For those who want to check: each point links to the official documentation page it comes from.
Google Calendar can notify an outside program on its own whenever a watched calendar changes — there is no need to keep re-reading the calendar.
Source: developers.google.com ↗ checked 2026-09-27There is an official query that returns only busy and available periods for a set of calendars — this is what lets an assistant pick a time without seeing the events themselves.
Source: developers.google.com ↗ checked 2026-09-27Inviting someone to an event puts a copy of that event on their calendar, and the invitee can accept or decline it.
Source: developers.google.com ↗ checked 2026-09-27A program can request only the entries that changed since its last check, which is how reschedules are picked up without re-reading the whole calendar.
Source: developers.google.com ↗ checked 2026-09-27Block Kit lets a message carry interactive elements such as buttons and menus; a message can hold up to 50 blocks.
Source: docs.slack.dev ↗ checked 2026-09-27An app may post about one message per second per channel, whichever way it sends them; short bursts above that are allowed.
Source: docs.slack.dev ↗ checked 2026-09-27The limits come from both systems. Slack lets an app post about one message a second into a channel, so when many meetings start at the same minute the reminders are queued and combined rather than sent one by one. Google limits how many requests a calendar takes per minute, both for the connection and per user, and slows the next minute when exceeded, so bulk changes are grouped and retried with a pause. Buttons and menus in a Slack message are limited to 50 blocks, which is enough for a day's agenda but not for a whole month in one message. Personal calendars take part only after each owner grants access themselves; we cannot read a calendar on someone's behalf.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →Automation & workspaceUSA meeting booked in your CRM lands in the manager's Google Calendar with an invitation to the client — and a change in the calendar goes straight back to the CRM
See scenarios →Automation & workspaceUSSlack as the team's alert desk: leads, deals and calls from the CRM land in a channel, and the team acts on them without leaving the chat
See scenarios →
↔A meeting planned in a Bitrix24 deal appears in the manager's Google Calendar with the client invited, and a move in the calendar comes back to the deal
See scenarios →
↔Mention the assistant in a Slack channel and Claude answers in the thread, reads the attached PDF and prepares draft replies that a person approves with a button
See scenarios →↔
Rows of a Google Sheet become Google Calendar events with guests invited, and every move or cancellation in the calendar is written back to the sheet
See scenarios →
↔Important Salesforce changes arrive in the right Slack channel as they happen, and a button in the message updates the record back in Salesforce
See scenarios →Implementation · Development · Integrations →
Google Calendar ↔ Slack — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.
