Skip to main content

​
Sign-in fails

If the Taack sign-in page shows an error, or you return to your AI app without being connected:
  • Use the owner’s account. Sign in with the Taack account that owns the committee. Patron accounts, and invited Members and Admins, can’t connect.
  • Allow pop-ups. Some browsers block the sign-in window. Allow pop-ups for your AI app and try again.
  • Check the server address. It must be exactly https://mcp.taack.app/mcp, including /mcp at the end.
  • Finish the approval. Close the sign-in page only after you approve access.
If it still fails, reconnect.

​
Reconnect the connector

Reconnecting starts a fresh sign-in. Try it when the assistant says it’s not authorized, when tools stop responding, or after you change your Taack password.
Go to Settings, then Connectors. Disconnect Taack, then connect it again and sign in.In Claude Code, run /mcp, select taack, and choose to re-authenticate. If that doesn’t help, remove and re-add it:

​
Your committee can’t be found

The connector works for the owner of a committee. If it asks you to finish onboarding or says your default committee cannot be found, complete onboarding or select your committee in Taack. To fix it:
  • New organizer? Sign in at taack.app and finish onboarding to create your committee. See Getting started.
  • Team Member or Admin? The connector is limited to the committee owner. Reconnect and sign in with that account.
  • Signed in with a different email? Reconnect and sign in with the account that owns the committee.

​
An event or plan can’t be found

The connector only sees events your account can manage. If the assistant can’t find an event:
  • Check that you’re signed in as the committee owner. Ask “Which Taack account am I connected as?”
  • Ask it to list your events, then pick from the list.

​
Results look incomplete

Some tools return a limited number of rows, and very large totals may stop early. When the connector truncates a result, the assistant should tell you. Treat the figure as a minimum, not a complete total. To get complete results:
  • Ask about one event at a time.
  • Filter by status, for example “past-due plans only”.
  • Ask for a specific patron by name or email.
Custom-question response lists show 25 matches by default and at most 50. Ask for a narrower answer filter or ask for answer totals instead. There is no next-page cursor. A list can show fewer rows than the number of matches even when the scan is not truncated. For complete sales figures, check Sales. For plans, open the event in Events, then choose More → Payment Plans. Review custom-question responses under Checkout or Registration on the event.

​
Totals don’t match the dashboard

  • Revenue looks low. The connector’s sales-summary revenue counts fully paid tickets only. It reports money collected on in-progress payment plans separately. Dashboard Online Earnings and Payouts can include collected plan payments before tickets are issued.
  • A combined total looks wrong. The connector never adds amounts in different currencies. If the assistant gives one total across TTD and USD, ask it to break the figures out by currency.
See How the connector reports money.

​
Question counts look different

  • More selections than answers. A multi-select question lets one attendee choose more than one option.
  • Payment plans appear in the count. Ask the assistant to separate paid and onPlan results. Held tickets are not fully paid sales.
  • The contact differs from the attendee. Response tools show the buyer’s contact details, which may differ from the person who answered.
  • Answers no longer match the options. Results put these under otherValues.

​
Next Steps changes look incomplete

Ask the assistant to read the event’s saved Next Steps back to you. Fields omitted from an update keep their previous values, but a supplied button list replaces the whole list. Include every button you want to retain. For an approval-required event, ask it to enable Show while approval is pending if you want Next Steps on checkout complete before approval for requests without a payment plan. Plan requests still need approval and a paid deposit. This affects that screen only. Pending-request emails and ticket pages still wait until the patron qualifies. Patron screens show the latest saved message. Emails already sent keep their original wording, and editing does not send a new notification. To view button tap counts, open Next Steps in the event’s Checkout or Registration tab; the connector does not return those counts. See Next Steps.

​
Still stuck?

Email hey@taack.app or visit taack.app/contact. Tell us which AI app you use and what the assistant said.