Docs

Recipes

Last updated: July 7, 2026

Ready-to-run workflows for an agent connected to Waydock over MCP. Each recipe lists the scopes it needs and the tools it calls, with a prompt you can adapt. New here? Start with the Quickstart and the Tool reference.

One rule to design around: once your turn reads untrusted content (an email body or a transcript), Waydock removes your write and send tools for the rest of that turn (provenance gating). So do any sending before you read untrusted bodies, or split reading and sending across separate turns.

1. Morning briefing

Answer "what's on my plate this morning?" from live context.

  • Scopes: read:briefing, read:cards, read:meetings
  • Tools: waydock_briefing, waydock_calendar, waydock_follow_ups_list

Prompt: "Give me a morning briefing. Summarize my pending cards, today's calendar, and anything I am waiting on other people for. Group by urgency and cite the source of each item."

To have Waydock compose and send the brief to your own inbox instead, use waydock_morning_brief_send (needs write:mail.send.self). Composing without sending is waydock_morning_brief_compose.

2. Follow-up chaser

See what you are waiting on and draft polite nudges, without sending automatically.

  • Scopes: read:meetings, write:mail.drafts
  • Tools: waydock_follow_ups_list, waydock_follow_up_nudge

Prompt: "List the commitments I am waiting on from other people in my recent meetings. For any unreplied email thread I point you to, draft a short, polite chase note and save it as a draft. Do not send anything."

waydock_follow_ups_list surfaces meeting action items where someone other than you is on the hook, so it needs read:meetings. waydock_follow_up_nudge drafts a chase email for an unreplied thread and saves it in your mailbox for you to review and send. That keeps the agent inside write:mail.drafts (which also grants read:mail) and never touches a send scope.

3. Meeting recap to tasks

Turn a meeting into tracked work.

  • Scopes: read:meetings, write:tasks
  • Tools: waydock_meetings_list, waydock_meeting_get, waydock_action_items_list, waydock_action_item_promote (or waydock_action_items_promote_bulk)

Prompt: "Take my most recent meeting. Summarize the decisions, then list the action items assigned to me and promote them to Linear in the 'Engineering' team."

Promoting creates the upstream Jira issue or Linear task. Use waydock_projects_list first if you need to confirm the exact project or team name.

4. Inbox triage

Clear the queue by acting on cards.

  • Scopes: read:cards, write:cards
  • Tools: waydock_inbox, waydock_card_get, waydock_card_action, waydock_card_feedback

Prompt: "Show my pending inbox cards. Archive newsletters and automated notifications, and flag anything from a real person that needs a reply. Explain each decision before acting."

waydock_card_action archives or snoozes; waydock_card_feedback records an important / not-important signal that tunes future triage.

5. Cross-source search

Answer a question that spans mail, meetings, tasks, and cards in one call.

  • Scopes: any one or more of read:mail, read:meetings, read:tasks, read:cards
  • Tools: waydock_search

Prompt: "Search everything for 'Acme renewal' and give me a single timeline of what has happened across email, meetings, and tasks."

waydock_search fans only into the verticals your key can read, so grant the read scopes for the sources you want covered.

6. Live mailbox lookup

Reach mail beyond the local index.

  • Scopes: read:mail.search, read:mail
  • Tools: waydock_mail_search, then waydock_mail_get

Prompt: "Search my mailbox for the latest invoice from Stripe and show me the full message."

waydock_mail_search returns provider message metadata; read a hit with waydock_mail_get (by emailId if archived, else by providerMessageId + accountId + provider). read:mail.search is a deliberate, separate grant from read:mail.

7. Send a summary to yourself

The safe outbound pattern, available on the free tier.

  • Scopes: read:briefing, write:mail.send.self
  • Tools: waydock_send_email

Prompt: "Summarize my day and email it to me."

write:mail.send.self can only reach your own verified inboxes. Sending to anyone else needs write:mail.send, which is a wildcard-proof, Pro-only, explicit grant, and every send obeys the outbound-email contract (allowlist, caps, kill switch).

Handling errors

Admission failures come back as an explicit code, so branch on it rather than retrying blindly:

  • insufficient_scope — the key lacks a required scope. Ask the user to add it.
  • upgrade_required — a paid write scope on a downgraded plan. Point the user to upgrade.
  • tool_blocked — the tool is on this key's denylist.

Send failures come back as a tool result flagged isError with a human-readable message (not a machine code), so surface the message and stop rather than retrying. Common causes: the daily cap or per-recipient cap was reached, a recipient is not on the allowlist, or sending is disabled (a paused account or the outbound kill switch).

Where to go next