Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
TypeScript agentaiai-agentsall-in-onecrmcrm-systememaillinearmcpmessagingnotesnotionofficerustslackslack-alternativestartupstartup-toolstypescriptworkspace
import {
useCalendarPromptAllowed,
useCalendarUiFlag,
} from '@app/features/calendar/hooks/use-calendar-ui-flag';
import { useKeyedPersistentToasts } from '@core/component/Toast/useKeyedPersistentToasts';
import { useUserId } from '@core/context/user';
import { useAddInboxFlow } from '@core/email-link';
import { fireAndForget } from '@core/util/fireAndForget';
import { useEmailLinksQuery } from '@queries/email/link';
/**
* Surfaces a per-inbox "Enable calendar" prompt for every linked inbox whose
* Google grant predates the calendar scope (or declined it), driven by
* `needs_calendar_permission` from the links list. Re-running the connect flow
* re-shows Google consent for the linked account and applies the upgraded
* grant to the existing link, which kicks off the calendar backfill.
*
* Only the viewer's own inboxes are prompted. The links list also carries
* inboxes another Macro user delegated to the viewer; whether that user's
* calendar syncs is theirs to decide, as in the calendar settings.
*
* Inboxes that also need a full reconnect are skipped so the two prompts don't
* stack. Reconnecting restores previously enabled calendar access too; an
* inbox that never enabled calendar can still opt in through this prompt.
* Inboxes whose calendar the user turned off are also skipped — that reads as
* missing calendar permission too, and nagging someone to re-enable what they
* just removed is the one thing this prompt must never do.
*
* Closing the prompt sticks across reloads. Nothing is broken while calendar
* is off, so re-asking every load is just nagging — Settings › Email keeps a
* per-inbox "Enable calendar" button for whenever the user wants it.
*/
export function CalendarPermissionPrompt() {
const calendarUiEnabled = useCalendarUiFlag();
const promptAllowed = useCalendarPromptAllowed();
const linksQuery = useEmailLinksQuery();
const userId = useUserId();
const startAddInbox = useAddInboxFlow();
useKeyedPersistentToasts({
items: () =>
calendarUiEnabled() && promptAllowed()
? (linksQuery.isSuccess ? linksQuery.data.links : []).filter(
(link) =>
link.macro_id === userId() &&
link.needs_calendar_permission &&
!link.needs_reauth &&
!link.calendar_disabled
)
: [],
key: (link) => link.id,
persistKey: 'macro:calendar-prompt:dismissed',
// Until the flag, the links and the viewer's id resolve, the empty list
// above means "don't know yet", not "no inbox needs this" — stored
// dismissals must survive that window.
itemsLoaded: () =>
calendarUiEnabled() && linksQuery.isSuccess && userId() !== undefined,
toast: (link, dismiss) => ({
title: 'Enable calendar',
content(): string {
return `Macro can now sync your calendar. Grant calendar access for ${link.email_address} to turn it on.`;
},
actions: [
{
label: 'Grant access',
onClick: () => {
// Suppress re-prompting until the grant upgrades; on native the
// page stays mounted while the OAuth flow runs.
dismiss();
fireAndForget(
startAddInbox({
scopes: 'calendar',
provider: link.provider,
reconnectLinkId: link.id,
emailAddress: link.email_address,
}),
'add-inbox'
);
},
},
],
}),
});
return null;
}