The temptation with integrations is to treat them as import pipes: pull everything in, own the copy, become the system of record. That is the wrong model for a calendar. Nobody wants a second calendar.
So these are two-way and deliberately narrow.
Google Calendar
Due-dated cards push to a calendar you choose. Events pull back as cards. Recurrence rules survive in both directions, so a weekly standup does not become fifty-two separate cards.
Neither side is authoritative. Edit in either place and the change travels.
We ask for calendar.events rather than full calendar access, which is enough
to create, read and update events and nothing about your calendar settings or
your other calendars. Google rejected our first verification for asking too
broadly, and they were right.
Google Sheets
A board can sync to a spreadsheet with an explicit column mapping, in both directions. Useful when someone in the loop lives in a spreadsheet and is not going to stop.
We ask for drive.file, which means access to files you specifically pick
through Google's own picker. Not your Drive; the sheet you chose.
Webhooks
Sixteen event types, signed with HMAC-SHA256 so your endpoint can verify the delivery is genuinely from us. Failed deliveries retry with exponential backoff, and every attempt is visible in a delivery log.
Configure them in Settings → Integrations.
Zapier and n8n
REST hooks with subscribe and unsubscribe, polling triggers, and actions for cards and boards, authenticated with an API key. This is the route for the long tail of "when X happens, do Y in a tool we have never heard of".
Canva
Connect a Canva account to import designs directly, or import individual designs by link or upload without connecting anything. See Whiteboards and Canva.
Availability
Integrations are a paid-tier feature. Setting one up needs a network connection and is one of the few things that does not work offline, since it is account configuration rather than your content.