What's new in OpenTag

CJ

Connect your CJ publisher account with your personal access token and company ID to ask about commissions, advertisers, links, and product feeds. An active publisher membership and access to the requested reports are required.

Fixed CJ reports failing on large pages or when otherwise identical commission items arrived in a different order. OpenTag can also read larger results more efficiently and keep the complete result available when a request resumes. Actual accounting conflicts still produce an explanation instead of silently accepting changed figures.

Open a custom MCP connection's details to see its server address and authentication method, such as OAuth or an API key. Sensitive parts of the address are hidden, with a notice when the displayed address is incomplete.

Fixed custom MCP connections offering an API key form when the service actually required a registered OAuth app. OpenTag now shows the callback URL and asks for your app's client ID and secret before opening the service's sign-in page. Existing connections can use the same setup when reconnecting.

Front

Connect Front to search and read conversations, tasks, contacts, and accounts from OpenTag. Setup requires your company's registered Front OAuth app credentials, with instructions linked from the connection form. The connection starts private; choose read-only access for lookups or read and write access to take actions such as adding comments.

Impact.com

Connect an Impact.com partner account with its Account SID and Auth Token to explore programs, actions, and available reports. You can add several accounts under separate names. Report access and actions such as creating tracking links depend on your account permissions and chosen connection access.

The Integrations directory now uses a flat list that prioritizes commonly connected apps within each connection section. Search and access filters still help you narrow the list and find the app you need.

OpenTag can now resume unfinished work after temporary model interruptions or when a response reaches its length limit, keeping the earlier conversation and completed actions available. Long answers continue from where they stopped before being delivered.

Fixed a problem that could stop routines, including end-of-day summaries, before they began working. A connected app offering an action with no valid choices no longer prevents OpenTag from using the other available actions.

Workspace owners and admins can now allow individual app connections in Slack Connect channels shared with clients or partners. Manage access from Integrations or ask OpenTag in a conversation, and revoke it when needed. Routines in those channels follow the same permissions.

If a request fails after sending a file to Slack, OpenTag now reports the confirmed delivery separately from the failure. Follow-up requests can find and reuse the generated file, including earlier CSV versions, so you can continue from the work already completed.

Statsig

Connect Statsig by signing in or using a Console API key to explore feature flags, configurations, experiments, metrics, and results. OpenTag works within your project's permissions, so you can review the information your account can access.

YC Bookface

Connect YC Bookface to search community information, read company documents and transcripts, and review hiring information from OpenTag. Sign in with a YC account enabled for MCP access, then choose read-only or read and write access. The connection starts shared with your team; you can make it private.