Integrations

Board events go out to Slack and webhooks. Items come in from email and the API.

TallyWeek has no marketplace. It has the four connections small teams actually wire up: signed webhooks, Slack messages, a calendar feed and a per-board email address.

Start free See pricingIncluded on the Free plan.

Webhooks and Slack, 7 events

Add a webhook from Workspace settings and every matching event is POSTed to your URL as JSON, signed with a secret you see once. Add a Slack incoming webhook and the same events arrive as messages with a button to open the item.

Each integration can listen to all events or a chosen few, on every board or only some. Send a test event, then read the last 50 deliveries with status and response time. After 20 failures in a row an integration pauses itself so a dead endpoint never slows the app.

  • Item created (item.created)
  • Status changed (item.status_changed)
  • Priority changed (item.priority_changed)
  • Column value changed (item.column_changed)
  • Item assigned (item.assigned)
  • Update posted (item.commented)
  • Item due today (item.due)

Zapier, Make and your own scripts

Zapier, Make and n8n all accept a webhook as a trigger, so any TallyWeek event can start a workflow there. To write back into boards, use the REST API on the Pro plan with a scoped key.

For your own code, verify the HMAC-SHA256 signature in the X-TallyWeek-Signature header against the raw body and the secret. The docs have a Node example.

Calendar feed

A personal iCal address for the items assigned to you, with due dates and timelines. Subscribe from Google, Apple or Outlook calendar; reset the link any time.

Email to board

Give a board its own address. The subject becomes the item name, the body its first update, filed into the group you choose.

REST API and MCP

Read and write boards from scripts and AI assistants with scoped keys, on Pro.

Questions

Are integrations on the Free plan?

Yes. Webhooks, Slack, the calendar feed and email to board are on every plan. The REST API and MCP server need a Pro key.

Is this a Slack app with slash commands?

No. TallyWeek posts to a Slack incoming webhook you create in Slack. Messages go one way, from TallyWeek to a channel. There are no slash commands and nothing to install in Slack beyond the incoming webhook.

How is a webhook signed?

Every delivery carries X-TallyWeek-Signature, which is sha256= followed by the hex HMAC-SHA256 of the raw request body using your integration's secret. X-TallyWeek-Event, X-TallyWeek-Delivery and X-TallyWeek-Timestamp are sent with it.

Are failed deliveries retried?

No. Each event is attempted once with a 5-second timeout and logged. Check the delivery log for the integration and fix the receiver; after 20 consecutive failures the integration pauses itself until you switch it back on.

What does the calendar feed include?

One all-day event per live item assigned to you that has a due date, across your workspaces. Items with a start date become multi-day events. Finished, archived and trashed items are left out.

Does email to board work out of the box?

It needs an inbound email domain configured by the operator of your TallyWeek instance. On tallyweek.com the address is shown in Workspace settings under Integrations once it is available.

Step-by-step instructions are in the docs.

Start a free workspace for your team.

14 days of Pro with no card, then Free for up to 3 members with every view and every automation.