Skip to main content

November 13, 2026 security incident

Last updated: November 15, 2026

On November 13, 2026, Assembled had a security incident involving the database that stores the credentials used to connect to third-party integrations. This page answers common questions, including what to do if your account is affected. Our team is here to help with any additional questions or with re-authenticating your integrations. Reply to any of our communications about the incident, or contact our support team.

About the incident

Is the incident contained? Is it safe to reconnect?

Yes. Our engineering and security teams have confirmed it’s safe to reconnect.

How do you know new credentials won’t be compromised the same way?

We cut off the attackers’ access before issuing new credentials, and we’re continuing to monitor our systems closely.

When did the unauthorized access begin, and how long did it last?

Unauthorized activity took place between 06:54 and 10:20 GMT on November 13. The attackers have been removed, and the access path they used has been secured.

What was accessed? Was our data accessed?

The attackers accessed the database that stores integration credentials. We’re treating all of those credentials as compromised. The root cause analysis will cover the full scope of what was accessed.

Is there evidence our credentials were used?

We haven’t found evidence that your credentials were used. We’re treating all stored credentials as compromised as a precautionary measure, which is why we revoked what we could and are asking you to replace the rest. We’re also working with our integration partners to review their access logs. The root cause analysis will explain how we reviewed credential activity.

Reconnect integrations and replace credentials

Which integrations did Assembled revoke?

We revoked these integrations:

  • Zendesk
  • Salesforce, including sandboxes
  • Google Drive
  • Google Calendar
  • Slack
  • Zoom Contact Center
  • Intercom
  • Notion
  • Five9
  • The keys used for authenticated chat (JWT)

Reconnect these in Configure > Third-party integrations. Google Calendar and authenticated chat work differently: see Google Calendar and authenticated chat below. If that system’s admin settings still show an active Assembled connection, revoke it there before reconnecting.

For every other connected integration on that page, create a new API key or password in that system, enter it in Assembled, then revoke the old one. Note when you did, so you can scope your log review.

I can’t find an option to disconnect Google Calendar on the Third-party integrations page. Am I in the right place?

Yes. There’s nothing to disconnect there. The Assembled → Google Calendar card holds settings only, so it always shows Connected. How to reconnect depends on how your team uses Google Calendar:

  • Personal calendar sync: each person reconnects their own Google Calendar from their own Assembled account. Admins can’t do this for them. See Reconnect after the sync is disconnected.
  • Team-wide calendar (Google Calendar → Assembled): most run on an Assembled-managed account, so there’s nothing to do on your side. We’ve revoked these and are reconnecting them for you. If your team-wide calendar uses a Google account your company owns, contact our support team and we’ll help you reconnect it.

Which integrations on our account were affected?

Treat every integration connected to Assembled as affected. Reconnect the integrations we revoked, listed above, and replace the credentials for every other integration, including AI agent tools and connectors.

How do we update our Okta client secret?

Generate a new client secret in Okta and share it with support@assembledhq.com through 1Password. Keep your current secret active until we confirm the update, then deactivate it.

What do we need to do for Workday?

Change the password for the integration user Assembled uses. Rotate any associated API credentials and update them in Assembled.

What do we need to do for AI agent tools and connectors?

Create new credentials and update them in Configure > Tools and connectors. Then revoke the old ones in that system. If a custom action calls a system you’ve reconnected, such as Zendesk, update its token too. Otherwise the action will fail.

What do we need to do for authenticated chat (JWT)?

We’ve revoked the JWT keys used for logged-in chat and issued new ones. Your engineering team will need to add the new key on your backend. Until it’s updated, chat won’t recognize logged-in users. Depending on your setup, this can affect personalization, workflows that use user details, and handoff.

To get your new key:

  1. Go to AI support > Chat agent, open the chat agent, and select the Setup tab.
  2. Under User data authentication, select Manage JWT Secret, and create a new JWT secret. Copy it: it’s shown only once.
  3. Update the secret on your backend.

For how your backend uses the secret, see Identify signed-in users.

Do we need to rotate our Assembled API keys?

No. API keys your team created in Assembled to call our API are stored hashed and don’t need to change. Credentials you saved in Assembled to connect to other systems are different. For each one, create a new API key or token in that system, replace the old one in Configure > Third-party integrations (or Configure > Tools and connectors for AI agent tools), then revoke the old key in that system.

Our MCP connection stopped working. What do we do?

Sign in again from your AI tool. If that doesn’t work, remove the Assembled connection from your MCP client, add it again, and sign in. Then run a tool that reads Assembled data to confirm you’re reconnected. For the steps in each AI tool, see Assembled MCP server setup.

Get help from our team

Can you share indicators of compromise or logs for our account?

Yes. Contact our team and we’ll share the indicators for your log review. We’ll also cover them in the root cause analysis.

Can we meet with your security team?

Yes. Reply to any of our communications about the incident, or contact our support team. Include who from your team should attend and a few times that work, with your time zone, and we’ll schedule time with our engineering and security teams.

Still have questions?