Integrations & API

A to-do API and meeting webhooks for Zapier, Make and n8n

A support form or Zapier adds to-dos to your SwitchDesk list in one HTTPS request; notes from recorded calls can go to your webhook.

Download for Mac

macOS 14.6 or later · 14-day free trial

A key per tool · One request per to-do · Standard Webhooks signatures

Read the developer docs →

Call Marlow & Finch back about the renewal

from Support form

1.Prep pricing slides for ThursdayFernhill

2.Reply to Daniel about the Q4 hiring planFernhill

3.Book Theo's dentist appointmentFamily

Send to-dos in

Plan: Incoming API, Pro

Each tool gets a key and adds to-dos to Incoming.

Answer four questions when you make the key, then hand its Docs tab to your developer or an LLM.

“Hand this to your LLM or developer. It follows this key's options, and your key is never in it: the code reads it from SWITCHDESK_API_KEY.”
Settings → Incoming to-dos

Skip

Name a key after the tool.

One key per tool. Its name is also the “from” label on everything it sends. The key shows once, so copy it then.

1Create an API keyYour API keys

One key per tool. Name it after the tool that will use it: the name is also the “from” label on its to-dos.

No keys yet.

Support formsdk_••••… · never used · Not set up yetRevoke

Key name, e.g. Slack botCreate key

Your new key for “Support form”Not copied yet

Copy it now. For your security it won't be shown again. Store it as the SWITCHDESK_API_KEY environment variable where the code runs.

sdk_••••••••••••••••••••••••••••

Copy keyDone

Next: four quick questions for this key, just below.

Answer four questions, all optional.

Where its to-dos go, what they say they’re from, whether it might send one twice, and whether it hears back when you finish one.

2Choose options for “Support form”

Four quick questions, all optional. Your answers are saved to this key and rewrite its documentation below. Question 4 also switches on calls from SwitchDesk to the tool.

1Where should new to-dos go?

Top of my listThey wait in Incoming, above Today's Todo, until you sort them.

Pre-assign a categoryFernhill

Each one arrives tagged “Fernhill”. File it there in one click, or send it to Today and it keeps the tag.

Straight into a categoryThey land at the bottom of one category you pick.

Let the builder decide each timeThe code chooses Incoming or a category for each item.

2What should they say they’re from?Support form

Support formEach item will show “from Support form”.

3Could the same item be sent twice?No, each item is sent once

Yes, it might resend thingsRe-scans, retries, polling. The docs require an id so repeats are ignored.

No, each item is sent onceThe docs keep the id optional, for retries only.

4Tell the sending tool when you finish an item?Yes, call its web address

NoNothing is sent back. Its code can still check an item's status when it needs to.

Yes, call its web addressSeconds after you check off, uncheck, start or delete an item this key sent, SwitchDesk calls an address the tool's developer gives you.

Hand the docs to your developer or an LLM.

“Copy docs” copies instructions written for this key’s answers. Change an answer and the docs change with it.

3Documentation for “Support form”

Hand this to your LLM or developer. It follows this key's options, and your key is never in it: the code reads it from SWITCHDESK_API_KEY.

Copy docs

# Send to-dos to my SwitchDesk to-do app Write code that sends to-dos into my SwitchDesk to-do list over HTTPS and, when needed, marks them in progress or done. Everything you need is below; follow it exactly. ## This key's setup These choices were made in the app for the key named "Support form". Follow them exactly; the sections below spell out each one. - Where items go: Incoming, at the top of my list, tagged with my "Fernhill" category. - Label: send `"source": "Support form"` on every item. It shows as "from Support form". - Repeats: each item is sent once, so `external_id` is optional. - Hearing back: on. When I finish, reopen, start or remove an item this key sent, SwitchDesk calls your code. Build the receiver described in When I finish an item.

Send a test item

Back to options

Its to-dos wait at the top of your list.

Each one arrives in Incoming, “from Support form” and tagged Fernhill, until you sort it.

Call Marlow & Finch back about the renewal

from Support form

Incoming to-dos

Let other tools send to-dos into SwitchDesk: Slack, email, Zapier, or a script an AI writes for you. Three steps: create a key, choose its options, then copy its documentation for your LLM.

1Key
2Options
3Documentation

1Create an API keyYour API keys

One key per tool. Name it after the tool that will use it: the name is also the “from” label on its to-dos.

No keys yet.

Support formsdk_••••… · never used · Not set up yetRevoke

Key name, e.g. Slack botCreate key

Your new key for “Support form”Not copied yet

Copy it now. For your security it won't be shown again. Store it as the SWITCHDESK_API_KEY environment variable where the code runs.

sdk_••••••••••••••••••••••••••••

Copy keyDone

Next: four quick questions for this key, just below.

2Choose options for “Support form”

Four quick questions, all optional. Your answers are saved to this key and rewrite its documentation below. Question 4 also switches on calls from SwitchDesk to the tool.

1Where should new to-dos go?

Top of my listThey wait in Incoming, above Today's Todo, until you sort them.

Pre-assign a categoryFernhill

Each one arrives tagged “Fernhill”. File it there in one click, or send it to Today and it keeps the tag.

Straight into a categoryThey land at the bottom of one category you pick.

Let the builder decide each timeThe code chooses Incoming or a category for each item.

2What should they say they’re from?Support form

Support formEach item will show “from Support form”.

3Could the same item be sent twice?No, each item is sent once

Yes, it might resend thingsRe-scans, retries, polling. The docs require an id so repeats are ignored.

No, each item is sent onceThe docs keep the id optional, for retries only.

4Tell the sending tool when you finish an item?Yes, call its web address

NoNothing is sent back. Its code can still check an item's status when it needs to.

Yes, call its web addressSeconds after you check off, uncheck, start or delete an item this key sent, SwitchDesk calls an address the tool's developer gives you.

3Documentation for “Support form”

Hand this to your LLM or developer. It follows this key's options, and your key is never in it: the code reads it from SWITCHDESK_API_KEY.

Copy docs

Send a test item

Back to options

Your answers are the defaults. A request that doesn’t say where it goes or where it’s from lands in Incoming, tagged Fernhill, “from Support form”.
Your tool can mark it done. One request sets it started or done, and never moves, renames or re-files it.
Today stays yours. No request can put a to-do in “Today’s Todo” or This Week; ☀ Today moves it in one press.

Signed status webhooks

Check off a to-do, and the sending tool hears about it.

Check off “Call Marlow & Finch back about the renewal” and, seconds later, the support form hears it’s done. Switch it on per key: “Tell the sending tool when you finish an item?”

POST Support formsends the to-do
INCOMING IncomingCall Marlow & Finch back… Today Fernhillfrom Support form
YOU Today Today's Todo1.Call Marlow & Finch back…
DONEToday's Todo1. Call Marlow & Finch back…status: done
CALL BACK Your URLtodo.status_changed

Fig. 1 One to-do from a support form, out and back. The call back is signed, and it says who changed it: "changed_by": "app".

The call your tool receives

JSON

{
  "id": "evt_4f1c2a9b0d3e4c5fa6b7c8d9e0f1a2b3",
  "type": "todo.status_changed",
  "occurred_at": "2026-09-23T18:04:11.482Z",
  "key_prefix": "sdk_••••",
  "data": {
    "id": "0d6f3c1e-8a2b-4c7d-9e1f-2a3b4c5d6e7f",
    "external_id": "slack:C0123ABCD:1712345.6789",
    "status": "done",
    "previous_status": "in_progress",
    "sequence": 3,
    "changed_by": "app"
  }
}

Signed. Standard Webhooks headers, so its libraries can verify every call.
Retried. A call that fails is retried with the same id over about 2 days. Answer 410 Gone to turn calls off.

Send meetings out

Plan: Meeting exports, Pro

Review a Fernhill call’s notes, then send them to your CRM.

“Send a copy of future calls in a category to a webhook — Zapier, Make, n8n, or your own server. Calls stay on this Mac; only what you pick is sent, and only calls that start after you set it up.”
Settings → Meeting exports

Shown in the Apricot theme

Edit meeting export

NameFernhill calls

CategoryFernhill Only calls filed in this category are sent. Today’s Todo and This Week can’t be exported.

Webhook addresshttps://hooks.example.com/••••Zapier, Make, n8n, or your own server. SwitchDesk signs every delivery; the address stays on our server.

What to send

SummaryThe AI summary of the call (written from the call and your notes)
Key pointsThe key discussion points
DecisionsDecisions that were made
Action itemsAction items and who owns them
My NotesYour own typed notes, word for word
TranscriptFull transcript (speaker names only when SwitchDesk could tell who spoke)
InviteesThe people on the calendar invite (not proof they joined)
DetailsTitle, date, duration and category

When

Ask me before each send
Send automatically (calls with a category you or your other calls set; AI-guessed categories still ask)

Team Teammates’ calls in this category use this export too — each teammate reviews on their own Mac first, and never sees the address or secret.

Pause all exports

While paused nothing is sent from any of your Macs. Calls that start during a pause are never exported; calls from before it go when you resume.

Lumora kickoff

Wednesday, 2:14 PM · 16:02Fernhill

Ready to send to Fernhill calls

Filed under Fernhill · set by you. Change it in the header if that’s wrong.

SummaryLumora wants a 12-seat pilot for its support team, starting next month. If it goes well they'd roll out to all 40 agents, so the next step is a revised proposal with pilot pricing by Thursday.

Decisions12-Seat Pilot: Start with Lumora's support team next month. Two-Week Check-in: Review the pilot with Joe two weeks in.

Action itemsSend Lumora the revised proposal by Thursday · Set up the pilot workspace · Book a pilot check-in with Joe two weeks in · Share the pilot pricing with Lumora before the pilot starts

Details: title, date, duration, category

Sent as: Sam Rivera, as who recorded it

Try it: press Send, or switch on “Pause all exports” first.

Fernhill callsAsks firstTeam

Fernhill → hooks.example.com

Summary, Key points, Decisions +2

Working · last sent 2 min. ago

Signing secret for ‘Fernhill calls’

Your endpoint uses this to check that a delivery really came from SwitchDesk (see “How to receive exports”).

whsec_••••••••••••••••••••••••Copy

You won’t see it again. Lost it? Make a new one from the export’s menu.

One secret per export. You see it once. “New signing secret…” replaces it, and the old one stops working at once.

Activity

All exports Refresh

Wed 2:31 PM	Fernhill calls	Lumora kickoff	Delivered	200
Wed 11:48 AM	Fernhill calls	Maya Chen’s call	Delivered	200
Tue 4:05 PM	Fernhill calls	Test send	Test	200

Signed, with no copy kept. SwitchDesk’s server signs and relays each delivery and stores none of it. SwitchDesk retries failed sends for up to 3 days, and the activity log shows how the address answered.

No key needed: add to-dos with Siri, paste call notes into Slack.

Ask Siri

Plan: Both plans

Say a task and SwitchDesk files it, or name a category and it goes straight there. Settings → Siri

Add a Todo

Speak a task. The AI picks a category, sizes it, and adds it to your list.

Hey Siri, talk to SwitchDesk
Hey Siri, add a todo to SwitchDesk
Hey Siri, new todo in SwitchDesk

Your categories

Hey Siri, add to Fernhill in SwitchDesk, …

Copy for Slack

Plan: Both plans

“Copy for Slack” keeps a call’s bold, bullets and ☐ action items when you paste. Recap has it on every section, next to “Copy for standup”.

Lumora kickoff

*Summary*
Lumora wants a 12-seat pilot for its support team, starting next month. If it goes well they'd roll out to all 40 agents, so the next step is a revised proposal with pilot pricing by Thursday.

*Action items*
☐ Send Lumora the revised proposal by Thursday
☐ Set up the pilot workspace
☐ Book a pilot check-in with Joe two weeks in

Pasted as plain text, it reads like this.

Lands in your to-do list

A support-form to-do lands in Incoming, then on Today’s list.

One press of ☀ Today moves it to the top of “Today’s Todo”, and it keeps its Fernhill tag.

POST /functions/v1/inbound-todos

from Support form

"text": "Call Marlow & Finch back about the renewal"

201 Created · Incoming · tagged Fernhill

Incoming1

Call Marlow & Finch back about the renewal

from Support form

Today's Todo

1.Prep pricing slides for ThursdayFernhill

2.Reply to Daniel about the Q4 hiring planFernhill

3.Book Theo's dentist appointmentFamily

This Week

What can I help with?

Animation added for this page.

Try it: after ↻ Replay, press ☀ Today, Week or Fernhill on the row yourself.

Also in SwitchDesk

Integration questions

Send to-dos in from the tools you already use.

Download for Mac

14-day free trial

Read the developer docs →