Guides

Connectors and settings

Bring in GitHub, Slack, calendars and more, and set notifications to suit how you work.

3 min read

Connectors in TabTasker

  1. 1Search connectors by name or by what they bring in, like issues, alerts or payments.
  2. 2Workspace connectors serve everyone and are set up by owners and admins. Only you ones, like calendars, Figma and Miro, link your own account.
  3. 3Show only what is Enabled, or what is Off, meaning paused.
  4. 4Your connections lists the connections you can see, who each is for, and its state, like On or Paused.
  5. 5Connectors sits at the foot of the main menu, between People and Settings.
  6. 6Each card says what a tool brings in and where it lands, here Chat, Tasks and Atlas. Calendars land in Agenda, and Commerce tools in the CRM.
  7. 7Its state, like Paused, with your setup saved. TabTasker Alerts beside it is Connected, with the day its last alert arrived.
  8. 8Manage opens a connector's settings. The switch pauses it, or turns it back On, without disconnecting.

Connectors

Connectors link TabTasker to the tools you already use: GitHub, Google and Microsoft calendars, Jira, Linear, Slack, Figma, Miro, payments and orders from Stripe, Shopify and Paddle, and alerts from your monitoring, like Sentry.

Some connectors are just for you, like calendars. Others work for the whole workspace and are set up by owners and admins. Most connectors can be paused from their card without disconnecting them.

Figma and Miro
Embed designs and boards in tasks and Atlas pages.

What the Free plan includes

A Free workspace has room for 2 projects, 65 tasks, 3 topics and one sprint at a time, 3 channels, 10 documents, 2 whiteboards, 2 decks, 2 workbooks and 10 slides in a deck. The CRM takes 8 companies, 20 contacts, 40 deals and 1 pipeline.

On Free, history older than 30 days in chat, activity and files is hidden, and it all comes back when you upgrade. Third-party connectors are on Business, while MCP is on every plan. A connection you made stays, but nothing syncs on Free: events that arrive meanwhile are not kept, and syncing resumes with new events when you upgrade.

AI credits start at 50, once per person. Proactive agent work pauses when the balance drops below 20, and what you ask for still runs.

Your settings

Settings covers your profile, sign-in methods, passkeys and two-factor authentication, devices, calls, date and time, appearance and navigation.

Settings, open on Account

  1. 1Search sections finds a section by its name or by what it holds: password finds Account, billing finds Plan & credits.
  2. 2Status sets how you appear to teammates in chat, calls and mentions. The Organization field switches to another organization or creates one.
  3. 3Profile holds your name, avatar and personal details. Account, open here, manages how you sign in, and Devices shows where you are signed in.
  4. 4Preferences set how TabTasker works for you, from Notifications and Calls to Date & time, Appearance and Navigation.
  5. 5Integrations connects AI assistants over MCP, your own scripts through the API and your own services with Webhooks.
  6. 6The Organization group holds settings for the whole workspace. Every member sees Labels, AI agents and Plan & credits; owners and admins also see Organization, Members, Squads and Usage, and owners see CRM.
  7. 7Sign-in methods shows your email and Email & password, and Connect adds Google, Microsoft or GitHub as another way in. Your last remaining method cannot be removed.
  8. 8Add a passkey to sign in with Touch ID, Windows Hello or your password manager instead of a password, in the browser and in the iOS app.
  9. 9Turn on two-factor to be asked for a code from your authenticator app when you sign in with your password. A passkey or a Google, Microsoft or GitHub sign-in skips the code.

Notifications and email

In Settings › Notifications, choose whether you are notified about every message, only mentions and direct messages, or nothing.

Quiet hours, at the foot of General, hold back alerts overnight while everything still arrives in the app. You can let some kinds through anyway, like incoming calls.

Email can be timely, a daily digest or off. Optional emails are limited in number and only sent during the day.

Notification settings

  1. 1Alerts set in Notifications apply to one workspace, here Acme.
  2. 2General holds the main choices, By type sets each kind of alert on its own, and Email sets your optional emails. Changes save automatically.
  3. 3Allow notifications lets this browser show alerts on your desktop.
  4. 4Hidden people lists who you hid with Hide person on their person card. Their message notifications stop in this workspace, and they are not told.
  5. 5Notify me for sets how much reaches you: Every message, Mentions and direct messages or Nothing. Everything still lands on your notifications page for 7 days.

Quiet hours

  1. 1Quiet hours sits at the foot of General. It holds back the interruption, not the notification: everything still arrives in the app.
  2. 2Silence notifications overnight turns quiet hours on or off.
  3. 3From and until set the window.
  4. 4Let these through anyway picks what may still interrupt you, by kind. Here Incoming calls and An agent is waiting on your approval break through.
  5. 5The times keep the time zone they were saved in, so quiet hours do not move when you travel.

Email notifications

  1. 1Email sets the optional emails TabTasker sends you.
  2. 2Email notifications apply across all your workspaces. Push and in-app alerts are set separately.
  3. 3Activity emails come Timely, as a Daily digest, or Off.
  4. 4Workspace tips help with a first workspace. Invitation reminders send one follow-up before an invitation expires.
  5. 5Optional emails are capped at 1 in any 24 hours and 4 in any 7 days, and only sent in the daytime, outside your quiet hours.

MCP, API tokens and webhooks

Settings › MCP connects AI assistants such as Claude, ChatGPT or Codex, on every plan. You sign in through the browser, so there is no token to copy. For CI, scripts or a client without browser sign-in, its Advanced section makes an MCP token instead.

On Business, Settings › API issues tokens for the REST API. Either kind of token belongs to one organization and is shown only once, so copy it straight away, keep it like a password and revoke it if it leaks.

Settings › Webhooks, also on Business, sends events to your own endpoint as they happen. Sign deliveries is on from the start: each delivery then carries a signature, so you can check it came from TabTasker. The signing secret is shown only once, when you create the webhook. The developer docs describe the REST API and list the tools an assistant can use over MCP.

Connect an AI assistant over MCP

  1. 1MCP works on every plan, while API below it needs the Business plan.
  2. 2Explore available tools opens the list of tools an assistant can use in TabTasker.
  3. 3One server URL for every assistant. Copy URL and add it to your client.
  4. 4Pick your assistant. Codex, ChatGPT, Claude, Claude Code and the rest each have their own steps.
  5. 5The setup guide follows the client you picked. Official guide opens its setup docs on the web.
  6. 6You sign in with your TabTasker account in the browser and choose the organization. No token to copy: a token is only for CI, scripts or a client without browser sign-in.

A new MCP token, shown once

  1. 1Made with Create token under Advanced: tokens for scripts and automation. A new token is shown only once: after Done it cannot be seen again.
  2. 2Copy token and keep it like a password. It acts with your permissions in this organization.
  3. 3Example: Claude Code adds the server with the token in the Authorization header. Any client that can set a header works the same way.
  4. 4Keep the token out of your repository. In CI, set the header from your secret store.
  5. 5Connections and tokens lists the assistants you connected, here Codex and Claude, and the tokens you made, here the new Release CI.
  6. 6When each one was Created, when it Expires and when it was Last used. A sign-in lasts 90 days, a token until the date you chose.
  7. 7Revoke stops its access on the next request. Revoke a token straight away if it leaks.

A new outgoing webhook, signed

  1. 1Webhooks, like API, needs the Business plan.
  2. 2New webhook opens a blank form in place of the selected webhook.
  3. 3Owners and admins choose a Direction, starting on Incoming · post to a channel. Outgoing · send to a service sends events from TabTasker to your endpoint.
  4. 4Give it a Name, and the URL of your endpoint: a public https address.
  5. 5Areas sets which events it sends: Tasks, CRM or both. It sends only what you can access yourself.
  6. 6Sign deliveries is on from the start: every delivery then carries a signature, so your endpoint can check it came from TabTasker. Signing cannot be added later.
  7. 7Create webhook saves it and shows its signing secret just once: Copy secret before Done, as no page can show it again. Its first events can take up to a minute to start.