Support

The support form is available at /support and /next/support. Use it when onboarding, connectors, exports, account access, or docs behavior is blocked.

Product reference

Find it at /support from the public site or /next/support from the app. Use the form fields to send a narrow reproduction path with route, workspace, connector status, and timing details.

Request fields

• email
• subject
• support message

Best support requests

• include org/workspace context
• include the exact route where the issue appeared
• describe connector status and last successful sync
• attach approximate timestamp when behavior changed
• include the source type, host, or browser if relevant
• say whether the problem happens in one workspace or every workspace

For connector issues, include whether the connector is active, pending, paused, or failing. For plugin issues, include the host (codex, claude_code, cursor, or remote MCP) and whether capture_session_signal is allowed.

What you get back

The form stores a support request and routes it into team review workflow with next-step guidance.

Support replies are easier to act on when the initial request has a narrow reproduction path. If the issue is urgent, include the route, workspace, connector, last known good time, and what changed immediately before the failure.

Before filing

Check the active workspace first. Many apparent missing-content or missing-signal issues happen because the workspace switcher is pointed at a different organization.

For connector problems, open /connectors and check status, authorization, last sync, and scope. For docs problems, include the docs route and whether search, navigation, or article body content is affected.

What not to include

Do not paste raw secrets, private keys, bearer tokens, or full customer data into support messages. Share narrow excerpts and route details instead.