Skip to main content
A connected account is the route to an original held by another service. Almanac keeps the connection and the account’s stable ID; the email, calendar, or meeting remains with its provider. Preserve both the account and native object ID as you move from search to read, citation, or a card in chat. An email address may be a unique account label, but the returned account ID is the durable identity.
list shows accounts available to tools. manage also shows connections needing attention or already disconnected; providers shows what can be connected. If a connection needs user action, accounts connect PROVIDER starts its authorization handoff and accounts reconnect ACCOUNT_ID repairs an existing connection. In an agent session with show_widget, a connections card can put that UI beside the conversation; the card itself does not authorize the account. A hosted agent already has its own Almanac identity, separate from these provider connections. For Gmail and Google Calendar, start with the owned email and calendar commands. Other capabilities are discoverable rather than a fixed list:
These are illustrative names and returned-ID placeholders, not a claim that your account has Granola connected. Search finds a capability; describe gives its current input schema and access requirements. Choose an account from the returned eligible accounts, and pass the input that schema requires. When several accounts can run a tool, the account ID is required. A write runs without a confirmation step, so it needs direct authorization for its effect before you call it, and a stable request key; external actions explains uncertain outcomes. A missing tool or disconnected account is an availability limit, not evidence that no original exists.