# Work with trax
Source: https://docs.traxy.ai/agent/overview

Use chat to find leads, review workspace information, and prepare campaigns.

Open **trax** and describe the outcome you want. Include the audience, topic, or lead you mean so trax can work with the right context.

Examples:

* “Show me warm leads at software companies.”
* “Find posts about hiring a first sales team.”
* “Review our lead criteria and suggest a narrower audience.”
* “Create a campaign for the leads in our founder view.”

## Search your leads or find new people

A lead search reviews people already in your workspace. The **Your matching leads** panel and counts marked **already in traxy** describe existing leads, not new discoveries. A short result list may show only the top matches.

To discover new people, ask for new leads or choose **Find more**. Review the discovery approval and remaining capacity before starting. Existing-lead searches do not consume capacity for new leads.

## Review results

The chat shows progress and the outcome of each action. Larger results, such as lead lists and campaigns, open beside the conversation. Open a lead to inspect its details and signal before deciding what to do next.

For a specific LinkedIn post, include its URL and explain whether you want to inspect the post, find similar posts, or work with its audience.

## Approve actions

When the Agent proposes an action that needs approval, inspect the card before selecting **Approve** or **Decline**. Configuration changes show the proposed values. Discovery requests show capacity information. Contact requests identify the lead and the requested contact data.

A draft or recommendation is not a completed change. Check the action's result after approval. Campaigns have a separate [test and launch review](/campaigns/review-and-launch).

## Manage a conversation

Use **New chat** to start another request. Open earlier chats from the **trax** menu. Pinned chats appear separately from conversations grouped by recency. You can rename, pin, or archive a chat from its menu.

Sharing a chat gives members of the same workspace read access through its link. They cannot reply or approve actions in your shared chat. Stop sharing when that access is no longer needed.

Use the stop control to end an active turn. Review any completed actions before asking the Agent to repeat the request.

## Review discovery runs

**Settings** > **Discovery runs** shows lead-discovery execution and history. Use [Discovery runs](/discovery/agent-runs) when you need to understand what discovery scanned or why it paused.

For the Agent's activity history, open **Settings** > **trax activity**. Review the recorded outcome before repeating an action.


# Memory and daily brief
Source: https://docs.traxy.ai/agent/preferences

Manage what the Agent remembers and configure your daily brief.

Open **Settings** > **Agent** to review memory and the daily brief.

## Manage memory

Memory helps the Agent keep useful context across conversations. Review saved entries and remove anything that is outdated or no longer relevant.

Personal memory applies to your own work. Workspace memory supplies shared context. Choose the intended scope when you ask trax to remember something; avoid adding sensitive information that other members should not use.

Memory is separate from **Lead criteria** and **Intent signals**. To change qualification, review and save the relevant targeting configuration.

## Configure the daily brief

Use the daily brief controls to choose whether it is enabled, its available delivery channel, and its delivery time. Review the destination before saving.

If you choose Slack, connect the intended workspace and channel first. If a brief does not arrive, check its enabled state and the Slack connection before changing your targeting.


# Authentication and scopes
Source: https://docs.traxy.ai/api-reference/authentication

Authorize the right workspace data and actions for REST or MCP.

## REST API keys

Send the workspace API key in the authorization header:

```http theme={null}
Authorization: Bearer trxy_live_...
```

An admin creates and revokes keys through **Integrations**. Review the scopes selected during creation; do not assume a key can read contact data merely because it can read leads.

## MCP OAuth

Authorize through the browser flow opened by your client. Select workspaces and approve the actions available to your current account permissions. A tool call must satisfy token scopes, the stored grant, current workspace membership, role, and product access.

OAuth refresh does not expand consent. Reauthorize to add workspaces or permissions. Losing access to the default workspace does not silently switch requests to another workspace.

## Supported scopes

A scope authorizes a capability; it does not imply that every capability is a REST endpoint. Read the endpoint or MCP tool contract for its required combination.

| Scope | Capability |
| - | - |
| `workspace:read` | Read workspace access, settings, and supported campaign, sender, and inbox information. |
| `leads:read` | Read visible leads and supported meeting records. |
| `leads:contact_read` | Read saved contact details and profile URLs. |
| `leads:contact_enrich` | Request contact lookups. |
| `leads:manage` | Manage leads, saved views, notes, tags, company research, and supported exports. |
| `analytics:read` | Read aggregate performance and meeting analytics. |
| `icp:read` | Read active targeting and its history. |
| `icp:manage` | Update the active ICP and Signal Brief. |
| `watchlist:read` | Read tracked profiles and summaries. |
| `watchlist:manage` | Manage tracked profiles. |
| `content:read` | Read content feeds. |
| `integrations:read` | Read integration and delivery state. |
| `integrations:manage` | Manage supported connections, delivery routes, webhook destinations, and integration settings. |
| `integrations:deliver` | Request delivery to a selected destination. |
| `sync:read` | Read synchronization and qualification status. |
| `agent:read` | Read discovery status, capacity, runs, and candidates. |
| `agent:run` | Run discovery and supported campaign, outreach, inbox, memory, and workspace-setting actions. |
| `post_qualification:manage` | Request qualification of a specific post. |
| `audience_analytics:read` | Read aggregate audience analytics. |
| `audience_analytics:request` | Request audience discovery. |

Contact enrichment also needs `leads:read` and `leads:contact_read`. Sending a lead to a webhook destination needs `integrations:deliver` and `leads:contact_read`. Creating, changing, or enabling a delivery route or webhook destination can also require `integrations:manage` and `leads:read`. ICP and Signal Brief updates need both `icp:read` and `icp:manage`.

Without contact permission, contact fields and profile URLs are redacted. Audience analytics returns aggregate information rather than individual contacts.

Request only what your integration needs, and review the actual scopes on each key or OAuth grant.


# Get active ICP configuration.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-active-icp-configuration

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/icp

# Get active ICP configuration through the active alias.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-active-icp-configuration-through-the-active-alias

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/icp/active

# Get aggregate analytics dashboard.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-aggregate-analytics-dashboard

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/analytics/dashboard

# Get aggregate lead stats.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-aggregate-lead-stats

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/leads/stats

# Get API-visible lead counts.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-api-visible-lead-counts

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/leads/counts

# Get business-facing workspace data access.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-business-facing-workspace-data-access

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/workspace-access

# Get integration status through the status alias.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-integration-status-through-the-status-alias

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/integrations/status

# Get latest qualification run.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-latest-qualification-run

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/qualification/runs/latest

# Get lead delivery state.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-lead-delivery-state

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/integrations/leads/{leadId}/delivery

# Get lead delivery state by query.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-lead-delivery-state-by-query

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/integrations/lead-delivery-state

# Get Meetings booked attribution counts.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-meetings-booked-attribution-counts

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/analytics/meetings
Uses the credential workspace and verifies its creator still has workspace read access. The feed omits meetingWith unless leads:contact_read is granted; source calendars and provider payloads are never returned.

# Get one account summary with top visible leads.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-one-account-summary-with-top-visible-leads

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/account-reports/{accountId}
Get one company account summary with top visible leads. Accepts a Company UUID or a legacy encoded company-name account ID.

# Get one API-visible lead.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-one-api-visible-lead

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/leads/{leadId}

# Get one monitored profile with safe relationship and follower metadata.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-one-monitored-profile-with-safe-relationship-and-follower-metadata

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/watchlist/profiles/{monitoredProfileId}

# Get one post summary, including safe postUrl and contentText.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-one-post-summary-including-safe-posturl-and-contenttext

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/analytics/posts/{postId}/summary

# Get safe integration status.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-safe-integration-status

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/integrations

# Get sync status.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-sync-status

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/sync/status

# Get watchlist summary.
Source: https://docs.traxy.ai/api-reference/customer-rest/get-watchlist-summary

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/watchlist/summary

# List account-level summaries derived from visible active leads.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-account-level-summaries-derived-from-visible-active-leads

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/account-reports
List company-level account summaries derived from visible active leads. Linked leads use Company UUID account IDs and unlinked leads retain legacy encoded name IDs.

# List API-visible leads.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-api-visible-leads

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/leads

# List attributed Meetings with snapshot cursor pagination.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-attributed-meetings-with-snapshot-cursor-pagination

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/meetings
Uses the credential workspace and verifies its creator still has workspace read access. The feed omits meetingWith unless leads:contact_read is granted; source calendars and provider payloads are never returned.

# List content feed posts, including safe postUrl and contentText.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-content-feed-posts-including-safe-posturl-and-contenttext

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/content-feed

# List content feed posts through the nested alias.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-content-feed-posts-through-the-nested-alias

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/content/feed

# List post analytics, including safe postUrl and contentText.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-post-analytics-including-safe-posturl-and-contenttext

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/analytics/posts
With monitoredProfileId, the page also carries `totals` (posts, reactions, comments and reposts of every post of that profile the other filters match, across all pages; never another profile's from monitoredProfileIds) and `latestPostAt` (that profile's latest recorded post, whatever the date filters).

# List qualified leads for one post.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-qualified-leads-for-one-post

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/analytics/posts/{postId}/qualified-leads

# List safe engagement summaries for one lead.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-safe-engagement-summaries-for-one-lead

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/leads/{leadId}/engagements

# List visible lead signals with safe lead, post, and watched-profile context.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-visible-lead-signals-with-safe-lead-post-and-watched-profile-context

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/leads/signals

# List watchlist profiles.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-watchlist-profiles

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/watchlist/profiles

# List watchlist recommendations.
Source: https://docs.traxy.ai/api-reference/customer-rest/list-watchlist-recommendations

/api-reference/customer-api-mcp-v1.openapi.yaml get /customer/watchlist/recommendations

# Approve or cancel MCP OAuth authorization from traxy.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/approve-or-cancel-mcp-oauth-authorization-from-traxy

/api-reference/customer-api-mcp-v1.openapi.yaml post /mcp/oauth/authorize/complete
Every active member may approve the requested actions permitted by their current role and MCP entitlement in the selected workspaces. Submitted scopes cap consent; each tool call also enforces the current role. Cancellation returns an access_denied callback.

# Exchange an authorization code or refresh token.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/exchange-an-authorization-code-or-refresh-token

/api-reference/customer-api-mcp-v1.openapi.yaml post /mcp/oauth/token
Supports authorization_code with PKCE S256 and refresh_token with rotation.

# Preview a pending MCP OAuth authorization request.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/preview-a-pending-mcp-oauth-authorization-request

/api-reference/customer-api-mcp-v1.openapi.yaml get /mcp/oauth/authorize/request

# Preview current account permissions in selected workspaces.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/preview-current-account-permissions-in-selected-workspaces

/api-reference/customer-api-mcp-v1.openapi.yaml post /mcp/oauth/authorize/permissions
Read-only authenticated preview. The request token stays in the body. Each workspace must pass current membership and MCP availability checks.

# Register a public MCP OAuth client.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/register-a-public-mcp-oauth-client

/api-reference/customer-api-mcp-v1.openapi.yaml post /mcp/oauth/register
Dynamic Client Registration for public clients. Redirect URIs must be safe loopback URIs or explicitly allowlisted HTTPS origins.

# Revoke an MCP OAuth token.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/revoke-an-mcp-oauth-token

/api-reference/customer-api-mcp-v1.openapi.yaml post /mcp/oauth/revoke

# Start MCP OAuth authorization.
Source: https://docs.traxy.ai/api-reference/mcp-oauth/start-mcp-oauth-authorization

/api-reference/customer-api-mcp-v1.openapi.yaml get /mcp/oauth/authorize
Validates client, redirect URI, resource, scopes, and PKCE challenge, then redirects to the traxy consent screen.

# MCP GET sessions are not enabled in V1.
Source: https://docs.traxy.ai/api-reference/mcp/mcp-get-sessions-are-not-enabled-in-v1

/api-reference/customer-api-mcp-v1.openapi.yaml get /mcp

# Streamable HTTP JSON-RPC endpoint for remote MCP clients.
Source: https://docs.traxy.ai/api-reference/mcp/streamable-http-json-rpc-endpoint-for-remote-mcp-clients

/api-reference/customer-api-mcp-v1.openapi.yaml post /mcp

# MCP tools
Source: https://docs.traxy.ai/api-reference/mcp/tools

Reference the public traxy MCP tool catalog, required scopes, and action requirements.

The public catalog contains 234 tools before scope and workspace filtering. Use `tools/list` to discover the tools and argument schemas your connection can actually use.

Each row lists all required scopes. Current workspace roles, product access, and action-specific checks still apply. Seeing a tool in the catalog does not grant permission to use it in every workspace.

Tool names retain `watchlist`, `organization`, and other established names where those are part of the public contract. In the app, watchlist profiles are tracked people or companies, and an organization is a workspace.

## Workspace, members, and profile

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_list_workspaces` | List accessible, authorized workspaces. | `workspace:read` |
| `traxy_get_workspace_access` | Read visible access and usage information. | `workspace:read` |
| `traxy_get_mcp_connection_status` | Read safe connection diagnostics. | `workspace:read` |
| `traxy_get_workspace_settings` | Read workspace settings. | `workspace:read` |
| `traxy_get_workspace_team` | Read the team. | `workspace:read` |
| `traxy_get_my_profile` | Read your profile. | `workspace:read` |
| `traxy_get_invite` | Read the invitation. | `workspace:read` |
| `traxy_get_member` | Read the member. | `workspace:read` |
| `traxy_set_auto_enrich_email` | Turn automatic email enrichment on or off. | `agent:run` |
| `traxy_backfill_lead_emails` | Queue email lookup for existing leads. | `agent:run` |
| `traxy_set_workspace_name` | Rename workspace. | `agent:run` |
| `traxy_update_my_profile` | Update my profile. | `agent:run` |
| `traxy_update_my_email_preferences` | Update my email preferences. | `agent:run` |
| `traxy_invite_teammates` | Invite members. | `agent:run` |
| `traxy_resend_invite` | Resend invitation. | `agent:run` |
| `traxy_revoke_invite` | Revoke invitation. | `agent:run` |
| `traxy_change_pending_invite_role` | Change pending invitation role. | `agent:run` |
| `traxy_change_member_role` | Change member role. | `agent:run` |
| `traxy_remove_member` | Remove member. | `agent:run` |
| `traxy_rename_team` | Rename team. | `agent:run` |
| `traxy_add_team_member` | Add team member. | `agent:run` |
| `traxy_change_team_member_role` | Change team member role. | `agent:run` |
| `traxy_remove_team_member` | Remove team member. | `agent:run` |
| `traxy_archive_my_chat` | Archive or restore my chat. | `agent:run` |

## Memory and daily brief

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_list_memories` | List memories. | `workspace:read` |
| `traxy_remember_for_me` | Remember for me. | `agent:run` |
| `traxy_remember_for_workspace` | Remember for the workspace. | `agent:run` |
| `traxy_forget_memory` | Forget a memory. | `agent:run` |
| `traxy_get_daily_brief` | Get daily brief settings. | `workspace:read` |
| `traxy_set_daily_brief` | Set daily brief. | `agent:run` |

## Leads, views, and contact data

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_list_leads` | List visible leads with supported filters. | `leads:read` |
| `traxy_get_lead_counts` | Read lead counts by tier. | `leads:read` |
| `traxy_get_lead_stats` | Read aggregate lead statistics. | `leads:read` |
| `traxy_find_leads` | Search existing workspace leads and return a matching count and ranked sample. | `leads:read` |
| `traxy_show_leads` | Show a selected set of workspace leads. | `leads:read` |
| `traxy_get_filter_values` | Get filter values. | `leads:read` |
| `traxy_list_lead_views` | List lead views. | `leads:read` |
| `traxy_save_lead_view` | Save a filter-based or fixed lead audience. | `leads:manage` |
| `traxy_get_lead` | Read one visible lead. | `leads:read` |
| `traxy_preview_lead_contact` | Preview lead contact lookup. | `leads:read`, `leads:contact_read` |
| `traxy_enrich_lead_contact` | Request and read persisted contact results. | `leads:contact_enrich`, `leads:read`, `leads:contact_read` |
| `traxy_list_lead_engagements` | Read recorded engagement summaries. | `leads:read` |
| `traxy_list_lead_signals` | Read lead signals with their available context. | `leads:read` |
| `traxy_apply_lead_action` | Apply a selected supported lead action. | `leads:manage` |
| `traxy_preview_bulk_lead_action` | Preview a bulk lead action. | `leads:read` |
| `traxy_bulk_lead_action` | Apply a lead action in bulk. | `leads:manage` |
| `traxy_list_account_reports` | List account reports. | `leads:read` |
| `traxy_get_account_report` | Read one account report. | `leads:read` |
| `traxy_add_lead` | Add a lead from LinkedIn. | `leads:manage` |
| `traxy_preview_set_lead_contact` | Preview a lead contact change. | `leads:read`, `leads:contact_read` |
| `traxy_set_lead_contact` | Set a lead's contact details. | `leads:manage`, `leads:contact_read` |
| `traxy_list_lead_tags` | List lead tags. | `leads:read` |
| `traxy_tag_leads` | Tag leads. | `leads:manage` |
| `traxy_update_lead_tag` | Rename or recolor a lead tag. | `leads:manage` |
| `traxy_delete_lead_tag` | Delete a lead tag. | `leads:manage` |
| `traxy_list_lead_notes` | List lead notes. | `leads:read` |
| `traxy_add_lead_note` | Add a lead note. | `leads:manage` |
| `traxy_update_lead_note` | Edit a lead note. | `leads:manage` |
| `traxy_delete_lead_note` | Delete a lead note. | `leads:manage` |
| `traxy_list_saved_lead_views` | List saved lead views. | `leads:read` |
| `traxy_update_saved_lead_view` | Edit a saved lead view. | `leads:manage`, `leads:read` |
| `traxy_delete_saved_lead_view` | Delete a saved lead view. | `leads:manage`, `leads:read` |
| `traxy_restore_deleted_leads` | Restore deleted leads. | `leads:manage` |
| `traxy_restore_done_leads` | Restore Done leads. | `leads:manage` |
| `traxy_delete_leads` | Delete leads. | `leads:manage`, `leads:read` |
| `traxy_export_leads` | Export leads to CSV. | `leads:manage` |

## Company research

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_check_company_research` | Request Meta ads and website-traffic research for companies. | `leads:manage` |
| `traxy_get_company_research` | Get company research. | `leads:read` |

## Discovery and search

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_find_hiring_people` | Find people who are hiring. | `leads:read` |
| `traxy_find_posts` | Find LinkedIn posts for a topic. | `leads:read` |
| `traxy_read_post` | Read post. | `leads:read` |
| `traxy_find_company_people` | Find people at a company. | `watchlist:read` |
| `traxy_get_agent_status` | Read lead-discovery status. | `agent:read` |
| `traxy_get_pipeline_capacity` | Read workspace pipeline capacity. | `agent:read` |
| `traxy_start_agent_run` | Start a confirmed discovery run. | `agent:run` |
| `traxy_list_agent_runs` | List discovery runs. | `agent:read` |
| `traxy_get_agent_run` | Get agent run. | `agent:read` |
| `traxy_cancel_agent_run` | Cancel agent run. | `agent:run` |
| `traxy_list_agent_candidates` | Read candidate summaries for a run. | `agent:read` |

## Targeting and blocklists

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_get_active_icp` | Read the active ICP. | `icp:read` |
| `traxy_update_active_icp` | Update selected active ICP fields. | `icp:manage`, `icp:read` |
| `traxy_list_icp_revisions` | Read ICP revision history. | `icp:read` |
| `traxy_get_active_signal_brief` | Read the active Signal Brief. | `icp:read` |
| `traxy_update_active_signal_brief` | Update selected Signal Brief fields. | `icp:manage`, `icp:read` |
| `traxy_list_signal_brief_versions` | Read Signal Brief version history. | `icp:read` |
| `traxy_get_discovery_agent_settings` | Get discovery Agent settings. | `agent:read` |
| `traxy_update_discovery_agent_settings` | Update discovery Agent settings. | `agent:run` |
| `traxy_generate_signal_brief` | Generate the Signal Brief. | `icp:manage`, `icp:read` |
| `traxy_list_company_blocklist` | List company blocklist. | `workspace:read` |
| `traxy_preview_company_blocklist` | Preview company blocklist changes. | `workspace:read` |
| `traxy_add_company_blocklist` | Add companies to blocklist. | `leads:manage`, `workspace:read` |
| `traxy_remove_company_blocklist` | Remove a company from blocklist. | `leads:manage`, `workspace:read` |
| `traxy_list_people_blocklist` | List people blocklist. | `workspace:read` |
| `traxy_preview_people_blocklist` | Preview people blocklist changes. | `workspace:read` |
| `traxy_add_people_blocklist` | Add people to blocklist. | `leads:manage`, `workspace:read` |
| `traxy_remove_people_blocklist` | Remove a person from blocklist. | `leads:manage`, `workspace:read` |
| `traxy_list_tracking_tags` | List Tracking tags. | `watchlist:read` |
| `traxy_create_tracking_tag` | Create a Tracking tag. | `watchlist:manage`, `watchlist:read` |
| `traxy_recolor_tracking_tag` | Recolor a Tracking tag. | `watchlist:manage`, `watchlist:read` |
| `traxy_set_content_calendar_auto_scan` | Set automatic post scanning. | `post_qualification:manage`, `content:read` |

## Tracking

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_track_profiles` | Track profiles. | `watchlist:manage` |
| `traxy_track_companies` | Track companies. | `watchlist:manage` |
| `traxy_track_posts` | Add single posts. | `watchlist:manage` |
| `traxy_list_watchlist_profiles` | List tracked people or companies with filtered totals. | `watchlist:read` |
| `traxy_get_watchlist_profile` | Read one tracked profile. | `watchlist:read` |
| `traxy_get_watchlist_summary` | Read tracking summary metrics. | `watchlist:read` |
| `traxy_list_watchlist_recommendations` | Read profile recommendations. | `watchlist:read` |
| `traxy_discover_profiles` | Discover profiles to track. | `watchlist:read` |
| `traxy_add_watchlist_profile` | Add a selected LinkedIn profile. | `watchlist:manage` |
| `traxy_update_watchlist_profile` | Update a tracked profile. | `watchlist:manage` |
| `traxy_remove_watchlist_profile` | Remove a tracked profile. | `watchlist:manage` |
| `traxy_restore_watchlist_profile` | Restore a removed tracked profile. | `watchlist:manage` |
| `traxy_list_tracked_posts` | List individual posts added by link. | `watchlist:read` |

## Content, analytics, and meetings

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_get_analytics_dashboard` | Read aggregate performance metrics. | `analytics:read` |
| `traxy_get_meetings_summary` | Read meeting summary counts. | `analytics:read` |
| `traxy_list_meetings` | Read attributed meeting records. | `leads:read` |
| `traxy_list_analytics_posts` | Read tracked-profile posts, with profile totals when requested. | `analytics:read` |
| `traxy_get_post_summary` | Read metrics for one post. | `analytics:read` |
| `traxy_list_post_qualified_leads` | List visible qualified leads for a post. | `analytics:read` |
| `traxy_list_content_feed` | Read visible feed posts. | `content:read` |

## Campaigns

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_get_outbound_planner` | Get the campaign plan. | `workspace:read` |
| `traxy_get_outbound_launch_preview` | Preview the campaign launch. | `workspace:read` |
| `traxy_inspect_campaign_leads` | Inspect campaign leads. | `workspace:read` |
| `traxy_probe_campaign_research` | Probe a research source. | `agent:run` |
| `traxy_draft_campaign` | Draft the campaign. | `agent:run` |
| `traxy_launch_campaign` | Launch the campaign. | `agent:run` |
| `traxy_get_lead_comments` | Get a lead's LinkedIn comments. | `workspace:read` |
| `traxy_test_outbound_plan` | Test the campaign. | `agent:run` |
| `traxy_approve_outbound_plan` | Approve the campaign. | `agent:run` |
| `traxy_set_outbound_play_live` | Turn the campaign on or off. | `agent:run` |
| `traxy_list_outbound_destinations` | List campaign destinations. | `workspace:read` |
| `traxy_set_outbound_destination` | Set the campaign destination. | `agent:run`, `integrations:deliver`, `leads:contact_read` |
| `traxy_set_outbound_delivery_mode` | Set the campaign delivery mode. | `agent:run` |
| `traxy_get_outbound_performance` | Get campaign performance. | `workspace:read` |
| `traxy_archive_outbound_campaign` | Remove a campaign. | `agent:run` |
| `traxy_reorder_outbound_campaigns` | Set campaign priority. | `agent:run` |
| `traxy_get_outbound_settings` | Get campaign outbound settings. | `workspace:read` |
| `traxy_set_outbound_sequence_destination` | Set a campaign native sequence destination. | `agent:run` |
| `traxy_set_outbound_runs_enabled` | Turn campaign outbound runs on or off. | `agent:run` |
| `traxy_create_outbound_heyreach` | Create a HeyReach campaign. | `agent:run` |
| `traxy_update_outbound_heyreach` | Update HeyReach campaign settings. | `agent:run` |
| `traxy_refresh_outbound_heyreach` | Refresh HeyReach campaign status. | `agent:run` |

## Messages, sequences, and senders

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_list_sequences` | List sequences. | `workspace:read` |
| `traxy_list_sequence_templates` | List sequence templates. | `workspace:read` |
| `traxy_get_sequence_template` | Get sequence template. | `workspace:read` |
| `traxy_create_sequence_template` | Create sequence template. | `agent:run` |
| `traxy_update_sequence_template` | Update sequence template. | `agent:run` |
| `traxy_archive_sequence_template` | Archive sequence template. | `agent:run` |
| `traxy_get_campaign_sequence_templates` | Get campaign sequence templates. | `workspace:read` |
| `traxy_set_campaign_sequence` | Set campaign sequence. | `agent:run` |
| `traxy_preview_switch_campaign_sequence` | Preview campaign sequence change. | `workspace:read` |
| `traxy_switch_campaign_sequence` | Switch campaign sequence. | `agent:run` |
| `traxy_get_sequence` | Get sequence. | `workspace:read` |
| `traxy_draft_outreach_message` | Draft a message. | `agent:run` |
| `traxy_list_outreach_senders` | List outreach senders. | `workspace:read` |
| `traxy_get_outreach_status` | Get outreach status. | `workspace:read` |
| `traxy_preview_outreach_message` | Preview a one-off message. | `workspace:read` |
| `traxy_send_outreach_message` | Send a one-off message. | `agent:run` |
| `traxy_list_senders` | List senders. | `workspace:read` |
| `traxy_open_sender_connect` | Open the connect flow. | `agent:run` |
| `traxy_set_sequence_senders` | Set who sends a sequence. | `agent:run` |
| `traxy_update_senders` | Change sender accounts. | `agent:run` |
| `traxy_remove_senders` | Remove sender accounts. | `agent:run` |

## Lead research and drafts

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_work_on_leads` | Research leads and draft messages. | `agent:run`, `leads:read` |
| `traxy_get_lead_jobs` | Get lead jobs. | `leads:read` |
| `traxy_rewrite_lead_message` | Rewrite a lead job's message. | `agent:run` |
| `traxy_stop_lead_jobs` | Stop lead jobs. | `agent:run` |
| `traxy_send_lead_jobs` | Send lead jobs to an integration. | `integrations:deliver`, `leads:contact_read` |

## Inbox and suppression

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_list_do_not_contact` | List do-not-contact entries. | `workspace:read` |
| `traxy_add_do_not_contact` | Add do-not-contact entry. | `agent:run`, `workspace:read` |
| `traxy_remove_do_not_contact` | Remove do-not-contact entry. | `agent:run`, `workspace:read` |
| `traxy_list_inbox_conversations` | List inbox conversations. | `workspace:read` |
| `traxy_get_inbox_conversation` | Read an inbox conversation. | `workspace:read` |
| `traxy_mark_inbox_conversations` | Mark inbox conversations read or unread. | `agent:run` |
| `traxy_archive_inbox_conversations` | Archive or unarchive inbox conversations. | `agent:run` |
| `traxy_pause_inbox_sequence` | Pause a lead sequence from the inbox. | `agent:run` |
| `traxy_resume_inbox_sequence` | Resume a lead sequence from the inbox. | `agent:run` |
| `traxy_stop_inbox_sequence` | Stop a lead sequence from the inbox. | `agent:run` |
| `traxy_unsubscribe_inbox_lead` | Unsubscribe a lead from the inbox. | `agent:run` |
| `traxy_reply_inbox_conversation` | Reply to an inbox conversation. | `agent:run` |
| `traxy_react_inbox_message` | React to a LinkedIn inbox message. | `agent:run` |
| `traxy_remove_sequence_enrollment` | Remove a lead from a sequence. | `agent:run` |
| `traxy_preview_instagram_contact` | Check an Instagram inbox contact. | `workspace:read` |
| `traxy_message_instagram_contact` | Message an Instagram contact. | `agent:run` |

## Billing

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_get_billing_summary` | Get billing summary. | `workspace:read` |
| `traxy_preview_billing_action` | Preview billing action. | `workspace:read` |
| `traxy_preview_billing_selection` | Preview billing selection. | `workspace:read` |
| `traxy_change_billing_selection` | Change billing plan and add-ons. | `agent:run` |
| `traxy_preview_legacy_phone_addon` | Preview legacy phone add-on. | `workspace:read` |
| `traxy_set_legacy_phone_addon` | Turn the legacy phone add-on on or off. | `agent:run` |
| `traxy_cancel_billing_subscription` | Cancel subscription. | `agent:run` |
| `traxy_pause_billing_subscription` | Pause subscription. | `agent:run` |
| `traxy_preview_billing_unpause` | Preview unpausing subscription. | `workspace:read` |
| `traxy_unpause_billing_subscription` | Unpause subscription. | `agent:run` |
| `traxy_resume_billing_subscription` | Resume cancelled subscription. | `agent:run` |
| `traxy_cancel_billing_scheduled_change` | Cancel scheduled billing change. | `agent:run` |

## Integrations and synchronization

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_get_integrations_status` | Read integration status. | `integrations:read` |
| `traxy_get_lead_delivery_state` | Read a lead delivery state. | `integrations:read` |
| `traxy_create_webhook_destination` | Create a selected webhook-style destination. | `integrations:manage`, `leads:read`, `leads:contact_read`, `integrations:deliver` |
| `traxy_set_webhook_destination_enabled` | Enable or disable a selected destination. | `integrations:manage`, `leads:read`, `leads:contact_read`, `integrations:deliver` |
| `traxy_deliver_lead_to_webhook_destination` | Queue one selected lead for delivery. | `integrations:deliver`, `leads:contact_read` |
| `traxy_get_sync_status` | Read synchronization status. | `sync:read` |
| `traxy_get_latest_qualification_run` | Read the latest qualification run. | `sync:read` |
| `traxy_get_hubspot_integration_settings` | Read HubSpot settings. | `integrations:read` |
| `traxy_get_slack_integration_settings` | Read Slack settings. | `integrations:read` |
| `traxy_list_slack_channels` | List Slack channels. | `integrations:read` |
| `traxy_get_google_calendar_settings` | Read Google Calendar settings. | `integrations:read` |
| `traxy_get_meta_ads_settings` | Read Meta Ads connection state. | `integrations:read` |
| `traxy_preview_meta_ads_export` | Preview Meta Ads export. | `integrations:read` |
| `traxy_update_hubspot_integration_settings` | Update HubSpot settings. | `integrations:manage` |
| `traxy_update_slack_integration_settings` | Update Slack settings. | `integrations:manage` |
| `traxy_create_slack_channel` | Create a Slack channel. | `integrations:manage` |
| `traxy_update_google_calendar_selection` | Select Google Calendars. | `integrations:manage` |
| `traxy_refresh_google_calendar_calendars` | Refresh Google Calendars. | `integrations:manage` |
| `traxy_update_google_calendar_notifications` | Update Google Calendar notifications. | `integrations:manage` |
| `traxy_start_meta_ads_export` | Start Meta Ads export. | `integrations:manage` |
| `traxy_list_webhook_destinations` | List webhook destinations. | `integrations:read` |
| `traxy_get_webhook_destination` | Get webhook destination. | `integrations:read` |
| `traxy_edit_webhook_destination` | Edit webhook destination. | `integrations:manage`, `leads:read`, `leads:contact_read`, `integrations:deliver` |
| `traxy_delete_webhook_destination` | Delete webhook destination. | `integrations:manage` |
| `traxy_list_delivery_routes` | List delivery routes. | `integrations:read` |
| `traxy_get_delivery_route` | Get delivery route. | `integrations:read` |
| `traxy_create_delivery_route` | Create delivery route. | `integrations:manage`, `leads:read`, `leads:contact_read`, `integrations:deliver` |
| `traxy_edit_delivery_route` | Edit delivery route. | `integrations:manage`, `leads:read`, `leads:contact_read`, `integrations:deliver` |
| `traxy_set_delivery_route_enabled` | Pause or resume delivery route. | `integrations:manage`, `leads:read`, `leads:contact_read`, `integrations:deliver` |
| `traxy_delete_delivery_route` | Delete delivery route. | `integrations:manage` |
| `traxy_get_heyreach_integration` | Get HeyReach integration settings. | `integrations:read` |
| `traxy_update_heyreach_integration` | Update HeyReach integration settings. | `integrations:manage` |
| `traxy_create_heyreach_list` | Create HeyReach list. | `integrations:manage` |
| `traxy_create_heyreach_campaign` | Create HeyReach campaign draft. | `integrations:manage` |

## Audience and post qualification

| Tool | Purpose | Required scopes |
| - | - | - |
| `traxy_get_audience_post` | Read aggregate post audience analytics. | `audience_analytics:read` |
| `traxy_find_audience` | Request aggregate audience discovery. | `audience_analytics:request` |
| `traxy_qualify_linkedin_post` | Request confirmed qualification for a post URL. | `post_qualification:manage` |
| `traxy_get_organization_audience` | Read aggregate workspace audience analytics. | `audience_analytics:read` |

## Confirm actions

Select the workspace, target, and action before making a write request. Use the returned preview and current schema rather than copying arguments from another tool.

* `traxy_start_agent_run` and `traxy_qualify_linkedin_post` require `confirmLeadUsage: true` after the user agrees that new qualified people may consume pipeline capacity.
* `traxy_apply_lead_action` supports `snooze`, `done`, `good`, `bad`, and `client`. The `done` action needs `confirmDone: true`. Preview bulk changes before applying them.
* Contact lookup needs an explicit request. Phone lookup applies only to eligible leads after activation. Saving manually supplied contact details is separate from enrichment.
* Read the current ICP or Signal Brief before updating it. Use its revision in requests that require one. Supplied arrays replace their earlier values; omitted fields stay unchanged.
* Preview campaign launch, message sending, billing, and destructive actions before confirming the intended change. A draft or preview does not authorize execution.
* Webhook destinations and delivery routes can send contact data outside traxy. Confirm the user’s intended host, audience, and destination before creating, changing, enabling, or sending to them.
* A queued delivery or lookup is not proof of completion. Read the resulting state before repeating a request.

The former `confirmCreditSpend` argument is not accepted. Sending it returns `validation_failed`; use only the current schema. The capacity tool replaces the former Agent budget-status tool.

See [workspace selection](/api-reference/mcp/workspaces), [authentication and scopes](/api-reference/authentication), and [error handling](/api-reference/pagination-and-errors) when building a client.


# MCP workspaces and protocol
Source: https://docs.traxy.ai/api-reference/mcp/workspaces

Select an authorized workspace for every MCP request.

One MCP connection can authorize up to 50 explicitly selected workspaces. The original default remains the default for calls that omit `workspaceId`.

## Select the workspace

1. Call `traxy_list_workspaces` to resolve accessible names and IDs.
2. Select the workspace named by the user. If several are available and none is clear, ask which one to use.
3. Pass its `workspaceId` on every scoped tool call, including pagination and follow-up actions.
4. Keep entity IDs and cursors tied to the workspace that returned them.

Example arguments for a lead read:

```json theme={null}
{
  "workspaceId": "11111111-1111-4111-8111-111111111111",
  "limit": 5
}
```

Use an actual ID returned by workspace discovery. There is no server-side active-workspace switch. Omitting the ID does not reuse the workspace from the preceding call.

## Handle access changes

If access to a selected workspace is lost, refresh the workspace list and explain the failure. Do not silently substitute another workspace. Reauthorize when the user wants to add a workspace to the consent set.

Listing or comparing several workspaces does not authorize writes to all of them.

## Protocol and tool discovery

traxy uses Streamable HTTP MCP and supports protocol versions `2025-06-18` and `2025-11-25`. Initialization echoes either supported version or selects `2025-11-25` when the requested version is unsupported.

`tools/list` filters the public catalog to the grant and currently accessible workspaces. A listed tool may still be unavailable in one particular workspace; each call rechecks permission there.

The schemas returned by `tools/list` are the exact argument contract for the active connection.


# Check Audience Analytics readiness for the key workspace.
Source: https://docs.traxy.ai/api-reference/ordinal-audience-analytics/check-audience-analytics-readiness-for-the-key-workspace

/api-reference/customer-api-mcp-v1.openapi.yaml get /audience-analytics/health

# Get aggregate audience breakdown for the key workspace.
Source: https://docs.traxy.ai/api-reference/ordinal-audience-analytics/get-aggregate-audience-breakdown-for-the-key-workspace

/api-reference/customer-api-mcp-v1.openapi.yaml get /audience-analytics/organization

# Get aggregate-only audience analytics for a LinkedIn post.
Source: https://docs.traxy.ai/api-reference/ordinal-audience-analytics/get-aggregate-only-audience-analytics-for-a-linkedin-post

/api-reference/customer-api-mcp-v1.openapi.yaml get /audience-analytics/linkedin-posts

# Request on-demand audience discovery for one exact LinkedIn post.
Source: https://docs.traxy.ai/api-reference/ordinal-audience-analytics/request-on-demand-audience-discovery-for-one-exact-linkedin-post

/api-reference/customer-api-mcp-v1.openapi.yaml post /audience-analytics/linkedin-posts/find-audience
Resolves the supplied LinkedIn reference to one immutable post, prepares an exact qualification quote, and accepts it as a pipeline-capacity request. Replays with the same idempotency key and payload reuse the durable request. An incompatible replay returns 409.

# API and MCP
Source: https://docs.traxy.ai/api-reference/overview

Choose REST reads or an OAuth-authorized MCP connection.

Use the public REST API for application reads. Use MCP when an AI client should read workspace data and perform supported, authorized actions.

| Connection | Authentication | Workspace selection |
| - | - | - |
| REST and audience analytics | API key | The key's workspace |
| MCP | OAuth access token | The authorized default or an explicit `workspaceId` |

> [card] [Make your first REST request](/api-reference/quickstart)
>
> Create a key and read a small lead sample.

> [card] [Connect an AI client](/integrations/ai-clients)
>
> Authorize workspaces and supported actions through OAuth.

> [card] [MCP tool reference](/api-reference/mcp/tools)
>
> Review public tools and action requirements.

> [card] [Handle results and errors](/api-reference/pagination-and-errors)
>
> Use continuation cursors and distinguish error types.

## Endpoints

REST base URL:

```text theme={null}
https://api.traxy.ai/api/v1
```

MCP endpoint:

```text theme={null}
https://api.traxy.ai/api/v1/mcp
```

Endpoint reference pages describe the public contract. The in-app Agent has additional capabilities that are not necessarily available through public MCP. Use the public tool catalog rather than assuming every app action has an MCP equivalent.


# Pagination and errors
Source: https://docs.traxy.ai/api-reference/pagination-and-errors

Read complete result sets and handle REST and MCP failures correctly.

## Paginate results

Cursor-based lists default to 50 results and accept at most 100 unless an endpoint states otherwise.

1. Make the first request without a cursor.
2. Read `page.nextCursor`.
3. Pass that exact value as `cursor` on the next request.
4. Keep the workspace, filters, and sort unchanged.
5. Stop when `page.nextCursor` is `null`.

Treat cursors as opaque strings. Do not decode, rebuild, or round their timestamp values. Invalid or incompatible cursors return `validation_failed`.

Some MCP tools use a ranked sample, an offset, or a bounded selection instead. Follow each tool's schema. `traxy_list_agent_candidates` uses `limit` and `offset`; `traxy_find_leads` returns a matching total and a ranked sample. Do not treat a sample as a complete export.

### Count tracked profiles and posts

`GET /customer/watchlist/profiles` accepts `entityType=PERSON` or `entityType=COMPANY`. Its `total` and `totalByEntityType` describe matches across pages. Use `sort=qualifiedLeads` to rank tracked profiles by their qualified lead count.

For `GET /customer/analytics/posts`, supplying `monitoredProfileId` adds `totals` for all matching posts from that profile. `latestPostAt` identifies its latest recorded post even when it falls outside the requested date range.

Account reports use a company UUID as `accountId` when the leads are linked to a company. Unlinked leads can retain an encoded company-name ID. Pass the returned ID unchanged when reading the account report.

## Filter lead results

Lead listing defaults to active leads. Use the documented disposition and filters for other views. A score filter narrows API-visible leads; it does not bypass qualification, deletion, blocklist, or workspace access rules.

Use lead-signal and engagement endpoints when you need the evidence behind a lead. Meeting analytics and meeting listing are separate endpoints; attendee details require contact permission.

## REST errors

REST failures use this envelope:

```json theme={null}
{
  "error": {
    "code": "invalid_api_key",
    "message": "Invalid API key.",
    "status": 401,
    "request_id": "req_example"
  }
}
```

| Status | What to check |
| - | - |
| `400` | Input validation and supported arguments. |
| `401` | Missing, expired, revoked, or inappropriate credentials. |
| `402` | Workspace access or required capability. |
| `403` | Scope, role, consent, or allowed origin. |
| `404` | Whether the resource exists and is visible in this workspace. |
| `409` | The operation-specific conflict described by the error code. |
| `429` | Rate limiting; follow retry guidance. |
| `503` | Temporary unavailability; follow `Retry-After` when supplied. |

## MCP errors

MCP has three error layers:

* Invalid HTTP bodies or authentication can fail at the HTTP layer.
* Unknown methods, unknown tools, malformed calls, or missing scopes can return a JSON-RPC error.
* A known, authorized tool with invalid arguments returns a normal result containing `isError: true`. Read `structuredContent.error.issues` for the paths to correct.

Do not treat every HTTP success as a successful tool action. Inspect the tool result and its error flag before continuing. An ambiguous write outcome is a reason to inspect state, not blindly repeat the action.


# REST quickstart
Source: https://docs.traxy.ai/api-reference/quickstart

Create an API key and retrieve your first traxy lead.

Create a key for the workspace your application should read.

## Create the key

1. Open **Integrations** > **API** as a workspace admin.
2. Choose **Create key** and enter a recognizable name.
3. Review the selected scopes. Include `leads:read` for lead reads and `leads:contact_read` when you need saved contacts or LinkedIn profile URLs.
4. Create the key, copy it once, and store it securely.

API access must be available to the workspace. If key creation is unavailable, review the displayed role or access requirement.

## Read one lead

Set `TRAXY_API_KEY` securely in your local environment, then request:

```bash theme={null}
curl --fail-with-body \
  'https://api.traxy.ai/api/v1/customer/leads?limit=1' \
  --header "Authorization: Bearer $TRAXY_API_KEY"
```

Records appear in `data`, with continuation information in `page`. An empty result means no API-visible lead matched that request; check the workspace, filters, and lead disposition.

Do not add `organizationId` or `workspaceId` to a REST request to select another workspace. Create and use a key for that workspace instead.

## Continue safely

Follow [pagination guidance](/api-reference/pagination-and-errors) for additional results. Store keys outside browser code and source control. Revoke a key through **Integrations** > **API** when it is no longer needed.

MCP uses [OAuth authorization](/api-reference/authentication), not this key.


# Create a campaign
Source: https://docs.traxy.ai/campaigns/create

Write a campaign yourself or work with trax to research an audience and prepare outreach.

Use a campaign to apply a research or messaging plan to a lead audience.

Campaign actions depend on your workspace's access and plan. If **Campaigns** shows an access or upgrade message, resolve it before trying to launch.

## Write a campaign

1. Open **Outbound** and choose **Create campaign**.
2. Name the campaign.
3. Choose the lead lists under **Audience**. With none selected, the audience is **All leads**. Use **See leads** to inspect it.
4. Write the message steps under **Sequence**, or select an available saved sequence.
5. Under **Senders and delivery**, choose senders with the accounts needed by every step. Check that sending is enabled.
6. Choose whether you approve each message or messages send automatically.
7. Review **Still needed** and resolve any issues before choosing **Launch campaign**.

Check that the draft shows **Saved**. If it changed elsewhere, reload it before continuing. Opening or saving a draft does not launch it.

## Build with trax

Start in **trax** when you want help with research, evidence, or messages written for each lead. Describe your audience, offer, and desired outcome. Identify the shared lead view and explain the research facts or message context you need. Review the plan and answer questions about missing information.

For example: “Use our shared founder view. Research how each company handles outbound, then draft a short LinkedIn introduction based on the evidence.”

## Choose what happens to results

A campaign can use the available integration, HeyReach, or sequence destination. Review the named destination, sender, and delivery mode. Research-only work does not require you to invent an outreach message.

Connecting a sender or destination is separate from authorizing launch. Use [Sender accounts](/outreach/senders) or [Integrations](/integrations/overview) to complete setup.

## Test a campaign built with trax

Ask trax to test the plan and inspect the results. A test prepares research and previews without sending outreach. Continue with [Review and launch](/campaigns/review-and-launch) when the sample meets your requirements.


# Manage campaigns
Source: https://docs.traxy.ai/campaigns/manage

Review campaign priority, progress, destinations, and lead outcomes.

Open **Outbound** > **Campaigns** to review active work and drafts. Open a campaign for its plan, funnel, destination, and the stage of each lead.

## Understand priority

Campaigns run in priority order. A lead goes to the first campaign it fits and is not researched or messaged by two unfinished campaigns at once. Review priorities when audiences overlap.

A campaign's shared views define its audience. You cannot delete or make those views personal while the campaign uses them.

## Review status

Check whether a campaign is live, paused, or needs a destination. Open an individual lead to understand whether it is being researched, awaiting approval, queued for delivery, or finished.

If a destination is unavailable or archived, choose a valid destination before expecting delivery to continue.

## Change or pause work

Use **Change with the Agent** to discuss a campaign change. Review the resulting proposal before approving it. A started campaign shows its own delivery mode, sender, and steps; those settings may be read-only in the panel.

Use the available pause control when you want to stop further work. Inspect active lead and delivery statuses after pausing; a message already sent cannot be recalled by pausing the campaign.

See [Campaign or message not progressing](/troubleshooting/campaigns-and-messages) for the checks to make before retrying.


# Review and launch
Source: https://docs.traxy.ai/campaigns/review-and-launch

Inspect campaign tests and approve the audience, messages, and destination.

For a campaign built with trax, review its test results in the campaign panel beside the chat. For a campaign you write in the builder, use **Review and launch** to inspect the audience, sequence, senders, and delivery mode.

## Review the test

Check whether the research supports each claim. Inspect missing or skipped results as well as usable drafts. Ask trax to revise the plan when it relies on the wrong audience, unsupported facts, or unsuitable wording.

A successful test does not mean a message was sent. Review the resulting preview and the campaign's next action.

## Launch the campaign

When the test finishes, open **Launch** and review:

* who will join the campaign
* leads excluded because another unfinished campaign holds them
* people contacted by a completed campaign before
* the selected sender or destination
* message steps and delivery mode

Confirm **Launch** only when these settings are correct. This is the campaign launch approval.

## Review messages that need approval

If the delivery mode requires approval, inspect leads in the campaign’s review queue. Review each message and its scheduled step before choosing **Approve** or **Approve all**.

You can edit a message before approving it. After an edit, choose **Save**, then approve the saved copy. **Cancel** discards the edit. If another member has changed or decided the message, refresh the approvals and review the latest version.

Changing the delivery mode to automatic does not release messages already waiting for approval. Review those messages separately.

Approval allows the next work to proceed; delivery can still wait for sender availability, schedule, limits, or other eligibility conditions. Check each lead's status to confirm the outcome.


# Discovery runs
Source: https://docs.traxy.ai/discovery/agent-runs

Review automated discovery, start a run, and inspect its results.

Open **trax** > **Discovery runs** to review discovery activity and pipeline capacity. You can also find this page under **Settings** > **Discovery runs**.

## Review discovery

Check whether discovery is active or paused and read any reason shown. Review the pipeline overview before requesting more leads.

A capacity stop and low supply need different responses. Capacity means the workspace has received its available leads. Low supply means discovery needs better or broader targeting and sources.

## Start and inspect a run

Use **Run now** when available, or ask the [Agent](/agent/overview) to find more leads and review its approval card.

Open a run to inspect its status, profiles scanned, results, and available candidate details. A scanned profile is not necessarily a qualified lead. Use **View leads** to review delivered results.

## If a run cannot start

Read the reason before retrying. Check workspace access, capacity, whether another run is active, and your targeting. Repeating a request does not bypass these conditions.

If discovery finds too few matches, refine [Lead criteria](/discovery/lead-criteria), review [Intent signals](/discovery/signals), or add relevant [tracked profiles](/discovery/tracking).


# Lead criteria
Source: https://docs.traxy.ai/discovery/lead-criteria

Define the people and companies that match your ICP.

Open **Targeting** > **Lead criteria** to describe who you sell to.

## Define your ICP

Use people criteria for roles, departments, seniority, and locations. Use company criteria for size, industry, revenue, and funding stage. Manage keywords and niches under **Intent signals**. Review the company and product context so traxy understands your offer.

Start with requirements that distinguish a buyer from a broad audience. For example, “sales leaders at software companies” is more useful than a long list of unrelated titles.

## Choose how strictly to match

Under **How strict should trax be?**, choose the approach that fits your audience:

* **Prioritize quality** requires matches to your selected job titles, locations, and company sizes.
* **Find more opportunities** requires location matches and uses titles, sizes, and industries to influence the score.

Both options check whether a company is a plausible buyer. Turn on **Advanced targeting** to choose **Required** or **Preferred** for individual criteria. Required criteria must match; preferred criteria influence fit without being mandatory.

Use the exclusion controls to rule out unwanted titles, locations, or company characteristics. Review exclusions alongside your included values so they do not conflict.

## Save a change

1. Review the existing criteria.
2. Change the fields that no longer describe your target buyer.
3. Review and save the update.
4. Inspect subsequent qualified leads and their fit reasons.

## Review existing leads after saving

After you save successfully, traxy can offer to check your active leads against the updated ICP.

1. Choose **Check leads** to start the review, or **Keep all leads** to leave them unchanged.
2. Wait for the check and review the number that no longer match.
3. Confirm the action to move those leads to **Done** only if you want to apply that result. Choose **Keep them** to leave them where they are.

Leads that cannot be checked stay where they are. A changed count needs another review before confirmation. If the check stops or fails, read the message before retrying.

Saving your criteria or running the check does not move leads by itself. Moving mismatches to **Done** keeps them available and does not change pipeline usage.

## Keep fit and signals separate

Lead criteria describe who fits. [Intent signals](/discovery/signals) describe the evidence you want to find. A relevant post does not make someone a qualified lead if they do not meet your criteria.

A lead-list score filter narrows the results you see. It does not change the qualification rules or create additional qualified leads.


# LinkedIn activity
Source: https://docs.traxy.ai/discovery/linkedin-activity

Find qualified leads from connected profiles and company-page activity.

Open **Targeting** > **Intent signals** > **LinkedIn activity** to choose which activity becomes leads for your workspace.

## Connect an account

1. Choose **Add LinkedIn account** and complete the connection flow.
2. Select the activity you want to collect: **Profile views**, **New followers**, and **New connections**.
3. Review the account’s connection status and enabled signals.

You can connect an account for activity collection without enabling outreach. Sending messages requires a sender with sending enabled. See [Sender accounts](/outreach/senders).

## Follow company-page activity

Under **Company pages**, review the pages available through your connected accounts. Turn on **Watch** for the intended page, then choose whether to collect **Followers**.

If a page is missing, check which LinkedIn account manages it. Follow the connection guidance to sign in again when traxy cannot retrieve its pages. Do not disconnect an account without checking the outreach that uses it.

Company-page follower collection is separate from [tracking a company’s public posts](/discovery/tracking).

## Review the resulting leads

In **Leads**, use the **LinkedIn activity** filter to choose the activity, connected account, and period. Activity must still meet your workspace’s qualification and capacity requirements before it becomes a new qualified lead.

A connected account can be collecting before matching leads appear. If it disconnects, earlier collected activity remains visible, but new activity waits for reconnection.


# How qualification works
Source: https://docs.traxy.ai/discovery/qualification

Understand fit, signals, feedback, and qualified lead delivery.

traxy evaluates people against your lead criteria and records the available signal context. Qualified leads become visible when your workspace can receive them.

## Understand fit

Qualification uses your required criteria, buyer fit, and an ICP match of at least 50%. Choose required and preferred criteria in [Lead criteria](/discovery/lead-criteria). Filtering for a higher score narrows your visible results; it does not change the qualification threshold.

Signal strength and ICP match answer different questions. Check both the person's fit and the evidence behind the lead before contacting them.

## Understand discovery sources

* **Discovery runs** discover people from your targeting and signals.
* **Tracked profiles** surface people through relevant post activity.
* **Single posts** let you request discovery for a particular LinkedIn post.
* **LinkedIn activity** can surface qualified people who view a connected profile, follow it, connect with it, or follow a selected company page.

The same person can have several recorded signals without becoming several new leads.

## Give feedback

Use **Good fit** or **Bad fit** and explain the reason. Feedback records your judgment; it does not directly rewrite the person's score. Review proposed targeting changes separately.

Actions such as **Done**, **Snooze**, and **Client** organize work. They are separate from fit feedback.

## Understand capacity

A person uses pipeline capacity when first delivered as a visible qualified lead in your workspace. Rediscovery, additional signals, export, enrichment, or restoring that lead do not count the person again.

When capacity is reached, new lead discovery pauses. Review [pipeline capacity](/workspace/plan-and-capacity) for what continues and how discovery resumes.


# Intent signals
Source: https://docs.traxy.ai/discovery/signals

Choose the topics and evidence that make a qualified lead relevant.

Open **Targeting** > **Intent signals** to review the Signal Brief that guides discovery.

Describe the problems, topics, or buying situations connected to your offer. Keep them specific enough to recognize in public activity. Review suggested topics before saving them.

## Configure the evidence you want

Review your business context, **Buyer pains**, **Buying triggers**, **Relevant topics**, and **Competitors**. Use **Relevance rules** to describe positive evidence and its weight. Save changes in the section you edit.

Use **Keywords & niches** for company terms that make a lead relevant. These terms complement the people and company criteria in [Lead criteria](/discovery/lead-criteria).

The **LinkedIn activity** section connects accounts and selects the activity you want to collect. Follow [LinkedIn activity](/discovery/linkedin-activity) to configure profile views, followers, connections, and company-page followers.

## Read a lead's signal

| Label | How to interpret it |
| - | - |
| **Warm** | A direct signal relevant to your offer. |
| **Related** | Contextual evidence related to your offer. |
| **Activity** | Observed activity with a weaker connection to your offer. |
| **ICP match** | Fit information without a recorded signal of the other types. |

These labels describe signal strength. They are separate from the ICP match score and the source that brought the person into traxy.

Open a lead's **Signals** tab to inspect recorded observations and available source links. Use the evidence actually shown when drafting a message. A missing signal does not prove that someone has no interest.

## Improve discovery

Change topics when the results consistently point to the wrong problem or audience. If the people themselves are wrong, revise [Lead criteria](/discovery/lead-criteria). Use [Tracking](/discovery/tracking) to add relevant profiles or specific posts.


# Track people, posts, and companies
Source: https://docs.traxy.ai/discovery/tracking

Manage the LinkedIn people, posts, and companies you follow.

Open **Targeting** and choose **People**, **Companies**, or **Single posts** under **Tracking**. Use **New** or its menu to track a profile, post, or company.

## Track a profile

1. Open **People** and choose **Track profile** from the **New** menu.
2. Paste its LinkedIn URL and verify the result.
3. Choose the relationship, such as competitor, teammate, influencer, investor, or custom.
4. Review and confirm the profile.

The initial discovery checks recent posts for new qualified leads. Those leads use your workspace's pipeline capacity. Adding the same profile again does not create another initial discovery.

For active profiles, ongoing monitoring follows a managed window of the five most recent posts published after the profile was added. Use a specific post request for older posts outside that window.

## Track a post

Open **Single posts** to inspect posts added by link and their qualified leads. Choose **Track post** from the **New** menu and paste a LinkedIn post URL.

Before confirming **Find leads**, review the candidate scope. Candidate counts describe people to evaluate, not a guaranteed number of qualified leads. Processing may take time; inspect the result before submitting the same request again.

## Track a company

Open **Companies** and choose **Track company** from the **New** menu. Review the company and relationship before confirming. Keep company tracking separate from the people you track individually.

## Review and manage tracking

Filter profiles by relationship or status. Open a profile or post to review its activity and qualified leads. Pause or remove a profile when you no longer want it monitored; use the available restore or resume action when appropriate.

The **Posts** tab inside a tracked profile shows that profile’s posts. **Single posts** holds the individual posts you added by link.

Counts across several posts can include the same person more than once. Use **Leads** to review the people themselves.

If no qualified leads appear, check [qualification](/discovery/qualification), profile activity, and [capacity](/workspace/plan-and-capacity).


# Join a workspace
Source: https://docs.traxy.ai/getting-started/join-a-workspace

Accept an invitation and start working with your team in traxy.

Join the workspace your team already uses so you can work with its shared leads and configuration.

1. Open the invitation email and follow its link.
2. Sign in or create your account using the invited email address.
3. Accept the invitation.
4. Check the workspace name before opening leads or changing settings.

Joining an existing workspace does not require you to create another ICP or complete new-workspace checkout. Your role and the workspace's access determine which actions are available.

## Start working with your team

Open **Leads** to review qualified leads and shared views. Use **trax** for a new request. Review [members and permissions](/workspace/team) before changing shared configuration.

If the invitation has expired or was revoked, ask an admin for a new invitation. If you already belong to several workspaces, use the workspace switcher to select the intended one.


# Find your way around
Source: https://docs.traxy.ai/getting-started/navigation

Navigate your workspace and replay the product tour.

Choose a section in the main navigation, then select a page or view from its menu. Expand the sidebar if you want to keep its labels and menu visible.

| Section | Where to go |
| - | - |
| **trax** | **New chat**, **Discovery runs**, and earlier chats |
| **Leads** | Built-in views, shared views, personal views, and **New view** |
| **Targeting** | **Lead criteria**, **Intent signals**, and tracked **People**, **Companies**, or **Single posts** |
| **Outbound** | **Inbox**, **Campaigns**, **Sender accounts**, and **Meetings** |
| **Insights** | Lead volume, trends, and audience patterns |
| **Settings** | Your profile, workspace, integrations, discovery settings, plan, and billing |

Available sections and actions depend on your workspace access and role. Open your account menu and choose **Settings** to manage your workspace.

## Take the product tour

Choose **Show me around** when the welcome appears. The tour follows the areas available to you. Use **Next** or **Back**, or choose **Skip tour** to continue on your own.

On a desktop-sized screen, open your account menu and choose **Product tour**. You can also open **Settings** > **Profile** and choose **Replay tour**. Replaying the tour does not reset your workspace or lead data.

## Check your workspace and capacity

Use the workspace switcher before changing shared targeting or campaign settings. The capacity indicator in the navigation opens **Manage lead capacity**, where you can inspect usage and the current period.

## Return to your work

Open **trax** to see pinned chats and conversations grouped by recency. Their status distinguishes work in progress, an approval waiting for you, and a new reply. Open **Leads** to return to a saved audience.


# Welcome to traxy
Source: https://docs.traxy.ai/index

Find qualified leads, run campaigns, and manage conversations with traxy.

Use traxy to find people who match your ICP, understand the signals behind each qualified lead, and turn that context into outreach.

Start with your company and targeting. Then ask trax to find leads or posts, review an audience, or help you build a campaign. You review proposed actions before they run.

> [card] [Set up your workspace](/quickstart)
>
> Review your targeting and find your first qualified leads.

> [card] [Work with trax](/agent/overview)
>
> Ask for research, lead discovery, and campaign help.

> [card] [Review your leads](/leads/overview)
>
> Understand fit, signals, contact details, and next steps.

> [card] [Create a campaign](/campaigns/create)
>
> Choose an audience, test your plan, and review it before launch.

## Choose where to work

| Area | What you do |
| - | - |
| **trax** | Start a chat, return to earlier conversations, and inspect discovery runs. |
| **Leads** | Review qualified leads and open built-in, shared, or personal views. |
| **Targeting** | Adjust lead criteria, intent signals, and tracked people, companies, or single posts. |
| **Outbound** | Work with Inbox, Campaigns, Sender accounts, and Meetings. |
| **Insights** | Review discovery results and audience patterns. |
| **Settings** | Manage your workspace, integrations, sender accounts, plan, and billing. |

See [Find your way around](/getting-started/navigation) for navigation and the product tour.

Connect other tools through [Integrations](/integrations/overview). For application development, use the [public API and MCP reference](/api-reference/overview).


# Connect an AI client
Source: https://docs.traxy.ai/integrations/ai-clients

Authorize a compatible MCP client to work with selected traxy workspaces.

Connect an AI client through MCP when you want to ask questions about traxy data or request supported actions from another application.

## Use the traxy connection guide

Open **Integrations** and select **Claude**, **ChatGPT**, or **Grok**. Follow the setup instructions for your client. The **ChatGPT** entry opens the Codex connection guide; see [ChatGPT and Codex setup](/integrations/codex).

For another compatible client, use its remote MCP setup instructions with the endpoint below. The client must support the connection and authorization method.

The remote MCP endpoint is:

```text theme={null}
https://api.traxy.ai/api/v1/mcp
```

Use OAuth authorization. A traxy REST API key is not accepted as an MCP credential. If a client needs a local bridge, follow that client's instructions shown in traxy rather than pasting a REST key into its configuration.

## Authorize workspaces

Choose the default workspace and any additional workspaces you want to authorize. Review the permitted actions for each workspace before approving.

Existing connections do not gain additional workspaces or scopes automatically. Authorize again when you need to expand access. Select the workspace explicitly in your conversation when more than one is connected.

## Confirm the connection

Ask the client to list your authorized workspaces, then read a small lead sample from the intended workspace. Review the result before requesting actions that modify data or start discovery.

Use the [MCP workspace guide](/api-reference/mcp/workspaces) for exact selection behavior and [connection troubleshooting](/troubleshooting/connections) for missing tools.


# Connect Claude
Source: https://docs.traxy.ai/integrations/claude

Authorize Claude to read traxy data and request supported actions.

Open **Integrations** > **Claude** in traxy and choose the app/browser or terminal instructions for your client.

## Connect with OAuth

1. Copy the MCP URL shown by traxy.
2. Add it as a remote custom connector in Claude using its available connector settings.
3. Start the connection and sign in to traxy when prompted.
4. Choose the default workspace and any additional workspaces.
5. Review the requested actions and approve the connection.
6. Return to Claude and confirm that the connector is available.

```text theme={null}
https://api.traxy.ai/api/v1/mcp
```

No traxy REST API key is required. For Claude Code, use the terminal setup shown in traxy's Claude integration page.

## Try a read first

Ask: “List my authorized traxy workspaces, then show five qualified leads from the workspace I select.”

Ask Claude to show proposed changes before applying actions or starting discovery. See [MCP tools](/api-reference/mcp/tools) for the public capabilities.

If a workspace or tool is missing, review the authorization scope and your current role. Disconnect through the client's connector settings when you no longer need the connection.


# Use Claude with a HeyReach workflow
Source: https://docs.traxy.ai/integrations/claude-and-heyreach

Combine traxy data access with a separately authorized HeyReach workflow.

Use the traxy connection to review lead evidence in Claude. Use a traxy route or campaign destination to move the selected audience into HeyReach.

1. [Connect Claude](/integrations/claude) to the intended traxy workspace.
2. [Connect HeyReach](/integrations/heyreach) and choose the destination.
3. Ask Claude to review a small audience and explain the evidence behind its selection.
4. Review the selected leads and proposed messages before authorizing delivery or launch.
5. Inspect HeyReach's campaign and sender configuration before outreach begins.

If you also connect HeyReach directly to Claude, follow the connection instructions in your HeyReach account. That authorization is separate from traxy's MCP connection.

For a native traxy campaign, an authorized MCP client can create and update campaigns, test a sample, review the launch preview, and request launch. The available actions depend on your granted scopes and workspace permissions. Follow [campaign review and launch](/campaigns/review-and-launch) and consult the [public tool reference](/api-reference/mcp/tools) before starting outreach.


# Clay
Source: https://docs.traxy.ai/integrations/clay

Send qualified lead events from traxy to your Clay table or workflow.

Use Clay to send signed lead events to your Clay table or workflow.

## Prepare the receiver

Create a webhook receiver and copy its HTTPS URL. Make sure the workflow can accept requests outside a temporary test session. Prepare an authentication header only if the receiver requires it.

## Connect and test

1. Open **Integrations** > **Clay**.
2. Enter a connection name and the HTTPS endpoint.
3. Add the required authentication header, if any, and save the connection.
4. Open **Settings** to review triggers and **Payload & help**.
5. Use **Send test payload** and verify the result at the receiver.
6. Open **Routes** to connect an audience to an endpoint and choose its delivery mode.

Follow [routing guidance](/integrations/routes) for automatic delivery, manual sends, and pause/resume behavior.

## Map and verify events

Use the payload samples in the app to map event metadata and available lead, company, contact, and engagement fields. First-delivery and repeat-engagement events have different purposes.

Requests include **X-Traxy-Signature** and **X-Traxy-Timestamp**. Follow **Payload & help** to verify signatures with the signing secret. If you rotate that secret, update your receiver before relying on later events.

An existing authentication header stays saved when its edit field is empty. Use the explicit removal action when you want to clear it.

## Handle failures

A test sends one immediate request. Lead delivery can retry temporary failures, so make downstream processing safe for repeated events.

Inspect both the delivery result and the receiver. Fix an expired URL, authentication failure, or unavailable workflow before resuming a paused route. Disconnecting stops future delivery through the connection; it does not delete records already received.


# Connect ChatGPT or Codex
Source: https://docs.traxy.ai/integrations/codex

Configure the traxy MCP connection in Codex and complete OAuth authorization.

Use a Streamable HTTP MCP connection to work with traxy from a supported ChatGPT desktop or Codex client. The connection uses browser OAuth.

In traxy, open **Integrations** and select **ChatGPT**. The connection page is titled **Codex** and provides app and terminal setup instructions.

## Connect from the CLI

With Codex installed, add the server:

```bash theme={null}
codex mcp add traxy --url https://api.traxy.ai/api/v1/mcp
```

Complete browser authorization if it opens. If authentication is still required, run:

```bash theme={null}
codex mcp login traxy
```

Choose the default workspace, any additional workspaces, and the actions you want to grant. Return to Codex when authorization completes.

## Connect from a desktop or IDE client

Open the client's settings and find **MCP servers** or the **MCPs** tab under **Plugins**, depending on your client version. Add a **Streamable HTTP** server named `traxy` and use the same URL. Save it, restart the connection if requested, and select **Authenticate** when offered. Leave bearer-token and custom authorization-header settings empty for this OAuth connection.

Codex clients on the same host can share MCP configuration. ChatGPT web uses its own plugin connection flow; a local CLI configuration does not connect the web client. See [OpenAI's MCP setup guide](https://learn.chatgpt.com/docs/extend/mcp) for the current client-specific steps.

## Verify and use the connection

Run `codex mcp list` to inspect configured servers. In a conversation, ask Codex to list the authorized traxy workspaces and read a few leads from the one you select.

Review [workspace selection](/api-reference/mcp/workspaces) before using several workspaces and [permissions](/api-reference/authentication) before requesting writes.


# Google Calendar
Source: https://docs.traxy.ai/integrations/google-calendar

Connect selected calendars to attribute meetings to traxy leads.

Connect Google Calendar so traxy can match calendar meetings to leads in your workspace.

1. Open **Integrations** > **Google Calendar**.
2. Connect the intended Google account and review its authorization request.
3. Select the calendars to use for attribution.
4. Save the selection and allow synchronization to complete.
5. Open **Meetings** to review matched results.

## Manage calendars

Review the selected calendars when you change accounts or team responsibilities. Refresh the calendar list if a calendar is missing. A removed calendar or rejected permission can stop its synchronization.

## Check a missing meeting

Confirm the Google account, selected calendar, date range, and sync status. Then review whether attendee information can match the lead or company. An event on a connected calendar is not automatically an attributed meeting.

Reconnect when authorization expires. Follow the displayed sync error if a calendar is no longer available or Google temporarily refuses access.

See [Meetings and outcomes](/reporting/meetings) for reviewing attribution and recording results.


# HeyReach
Source: https://docs.traxy.ai/integrations/heyreach

Route leads to HeyReach campaigns or lists and review delivery.

Connect HeyReach when you want leads to enter a HeyReach campaign or lead list.

## Connect HeyReach

1. Open **Integrations** > **HeyReach**.
2. Enter your HeyReach API key and connect.
3. Open **Routes** and choose a lead view.
4. Choose **Campaign** or **Lead list** and select the intended destination.
5. Review the delivery mode and save the route.

Complete the campaign's sequence and sender setup in HeyReach before relying on outreach there. A connected API key alone does not define a delivery destination.

## Choose the workflow

A route moves matching leads into the selected HeyReach destination. A traxy campaign can also use a HeyReach destination as part of its approved workflow. Review which workflow you are configuring before enabling automatic delivery.

HeyReach delivery needs a LinkedIn profile URL. Review the lead and delivery result if that information is missing.

## Review results

Use the integration's available performance information and per-lead delivery state. Sending a lead to HeyReach is different from HeyReach sending a message or receiving a reply.

Use [routing guidance](/integrations/routes) for existing leads and paused routes. Disconnect and reconnect when you need to change the API key. Disconnecting does not remove existing HeyReach leads or campaigns.


# Meta Ads
Source: https://docs.traxy.ai/integrations/meta-ads

Export qualified leads as an audience CSV for Meta Ads.

Use **Integrations** > **Meta Ads** to prepare a value-based audience CSV from eligible qualified leads.

## Prepare an export

1. Review the audience size and ICP match threshold in the app.
2. Select **New export** and inspect the audience snapshot.
3. Choose whether to use saved contact data or an available enrichment option.
4. Review contact eligibility and start the export.
5. Wait until the export is ready, then download the CSV.

Email and phone lookups follow your workspace's contact entitlements. More available identifiers can help matching, but lookup does not guarantee a contact result or a match in Meta.

## Use the file

Upload the CSV through the customer-list audience workflow in your Meta account. Follow Meta's current field mapping and audience requirements. Only use contacts you have permission to use for that purpose.

A completed traxy export means the file is ready. Meta processes and matches that file separately. Review its result before using the audience in advertising.

If the export fails, inspect the error and contact settings before retrying. Refresh the audience when your eligible lead data changes.


# n8n
Source: https://docs.traxy.ai/integrations/n8n

Send qualified lead events from traxy to your active n8n workflow.

Use n8n to send signed lead events to your active n8n workflow.

## Prepare the receiver

Create a webhook receiver and copy its HTTPS URL. Make sure the workflow can accept requests outside a temporary test session. Prepare an authentication header only if the receiver requires it.

## Connect and test

1. Open **Integrations** > **n8n**.
2. Enter a connection name and the HTTPS endpoint.
3. Add the required authentication header, if any, and save the connection.
4. Open **Settings** to review triggers and **Payload & help**.
5. Use **Send test payload** and verify the result at the receiver.
6. Open **Routes** to connect an audience to an endpoint and choose its delivery mode.

Follow [routing guidance](/integrations/routes) for automatic delivery, manual sends, and pause/resume behavior.

## Map and verify events

Use the payload samples in the app to map event metadata and available lead, company, contact, and engagement fields. First-delivery and repeat-engagement events have different purposes.

Requests include **X-Traxy-Signature** and **X-Traxy-Timestamp**. Follow **Payload & help** to verify signatures with the signing secret. If you rotate that secret, update your receiver before relying on later events.

An existing authentication header stays saved when its edit field is empty. Use the explicit removal action when you want to clear it.

## Handle failures

A test sends one immediate request. Lead delivery can retry temporary failures, so make downstream processing safe for repeated events.

Inspect both the delivery result and the receiver. Fix an expired URL, authentication failure, or unavailable workflow before resuming a paused route. Disconnecting stops future delivery through the connection; it does not delete records already received.


# Ordinal
Source: https://docs.traxy.ai/integrations/ordinal

Connect Ordinal to traxy by generating a dedicated Ordinal API key and adding it to the traxy integration in Ordinal.

Use the Ordinal integration when you want Ordinal to access your traxy audience data.

Set up starts in traxy. Generate a dedicated Ordinal API key from the Ordinal integration page, then add that key to the traxy integration inside Ordinal.

## Before you connect Ordinal

Admins can generate an Ordinal key in traxy.

Make sure you have:

* access to the traxy workspace you want to connect
* a workspace with API access available
* access to the Ordinal account you want to connect
* the Ordinal integration available in traxy
* a place to store the key securely

The key is specific to the Ordinal integration. Use it only for Ordinal.

## Generate the Ordinal key in traxy

1. Open the [Ordinal connection page](https://app.traxy.ai/integrations/ordinal) in the intended workspace.
2. Generate the Ordinal API key.
3. Copy the key when traxy shows it.
4. Store the key in your team's secret manager.

traxy shows the full key only once. If the key is lost, generate a new Ordinal key and update it in Ordinal.

## Add the key in Ordinal

1. Open Ordinal.
2. Go to **Integrations**.
3. Open the **traxy** integration.
4. Paste the traxy API key into the traxy integration.
5. Save or connect the integration.

After the key is saved in Ordinal, Ordinal can access the traxy data needed for its audience workflow.

## What Ordinal can read

Ordinal can access aggregate audience data available through the dedicated traxy key.

The integration can use:

* workspace audience breakdowns by industry, title, company size, or location
* aggregate audience analytics for LinkedIn posts tracked in your workspace
* post-level engagement counts and sync counts
* audience discovery status for a LinkedIn post

Ordinal responses are aggregate-only. They do not include individual people, emails, phone numbers, LinkedIn profile URLs, raw comments, or raw scraped data.

## API endpoint docs

Ordinal uses the dedicated traxy key as a bearer token with the `https://api.traxy.ai/api/v1` base URL.

Use these generated endpoint docs for exact query parameters, request bodies, response schemas, and status responses.

> [card] [Check readiness](/integrations/ordinal/readiness)
>
> `GET /audience-analytics/health`

> [card] [Get post audience](/integrations/ordinal/linkedin-post-audience)
>
> `GET /audience-analytics/linkedin-posts`

> [card] [Request audience discovery](/integrations/ordinal/request-audience-discovery)
>
> `POST /audience-analytics/linkedin-posts/find-audience`

> [card] [Get workspace audience](/integrations/ordinal/workspace-audience)
>
> `GET /audience-analytics/organization`

## Request audience discovery

If you select **Audience discovery**, Ordinal can request audience discovery for a LinkedIn post that belongs to a profile monitored in your workspace.

Audience discovery may return:

* **ready** when aggregate audience data is available
* **not requested** when discovery has not started
* **queued** when discovery has been queued
* **pending** when discovery is running
* **already available** when traxy already has the aggregate audience data

Audience discovery uses your workspace permissions and available pipeline capacity. If discovery is not available, review your workspace access and capacity before retrying.

## Keep access safe

Treat the Ordinal API key like a password.

* Store the key in a secret manager.
* Do not paste the key into docs, chat, analytics tools, or issue trackers.
* Revoke the key if Ordinal access changes or if you think the key was exposed.

Revoking an API key stops new Ordinal requests immediately. It does not delete existing aggregate analytics in traxy.


# Get LinkedIn post audience
Source: https://docs.traxy.ai/integrations/ordinal/linkedin-post-audience

api-reference/customer-api-mcp-v1.openapi.yaml GET /audience-analytics/linkedin-posts
Read aggregate audience analytics for a LinkedIn post tracked in the workspace.

Use this endpoint to read aggregate-only audience data for a tracked LinkedIn post.


# Check Ordinal readiness
Source: https://docs.traxy.ai/integrations/ordinal/readiness

api-reference/customer-api-mcp-v1.openapi.yaml GET /audience-analytics/health
Check whether a dedicated Ordinal API key can access audience analytics.

Use this endpoint before other Ordinal audience analytics calls.


# Request audience discovery
Source: https://docs.traxy.ai/integrations/ordinal/request-audience-discovery

api-reference/customer-api-mcp-v1.openapi.yaml POST /audience-analytics/linkedin-posts/find-audience
Queue audience discovery for a LinkedIn post or return existing aggregate audience data.

Use this endpoint when Ordinal needs traxy to discover the aggregate audience for a LinkedIn post.

Set `requalify: true` to evaluate the already-synced audience of a post against your current ICP when aggregate analytics already exist. This can use additional pipeline capacity for newly qualified leads. People already counted are not charged again. An in-progress request is returned instead of starting another.


# Get workspace audience
Source: https://docs.traxy.ai/integrations/ordinal/workspace-audience

api-reference/customer-api-mcp-v1.openapi.yaml GET /audience-analytics/organization
Read an aggregate audience breakdown for active leads in the workspace.

Use this endpoint to read aggregate workspace audience segments by title, company size, location, or industry.


# Integrations
Source: https://docs.traxy.ai/integrations/overview

Connect delivery tools, AI clients, calendars, and audience workflows.

Open **Settings** > **Integrations**. Choose a connection based on what you want to do with your workspace data.

| Goal | Connection |
| - | - |
| Send lead alerts | [Slack](/integrations/slack) |
| Send leads to an outreach destination | [HeyReach](/integrations/heyreach) |
| Start another workflow | [Webhook](/integrations/webhook), [Clay](/integrations/clay), [n8n](/integrations/n8n), or [Zapier](/integrations/zapier) |
| Work from an AI client | [Claude](/integrations/claude), [ChatGPT or Codex](/integrations/codex), or another [compatible MCP client](/integrations/ai-clients) |
| Attribute booked meetings | [Google Calendar](/integrations/google-calendar) |
| Analyze an aggregate audience | [Ordinal](/integrations/ordinal) |
| Export an advertising audience | [Meta Ads](/integrations/meta-ads) |
| Read data from application code | [REST API](/api-reference/quickstart) |

## Connect, then choose delivery

A successful connection does not mean leads are being sent. For lead-delivery integrations, configure [routes](/integrations/routes) that select an audience, destination, and delivery mode.

Review the route and connection state before relying on automatic delivery. Use a test event to check the receiving system, then inspect a real lead's delivery result.

Connection management, route changes, and API-key creation can have different permission requirements. Use the actions available to your current role and ask an admin when access is missing.


# Route leads to other tools
Source: https://docs.traxy.ai/integrations/routes

Connect a lead view to a destination and control automatic or manual delivery.

A route connects one audience to one destination. Use separate routes when different lead views should go to different channels, endpoints, campaigns, or lists.

## Add a route

1. Connect the integration and open its **Routes** tab.
2. Select **Add route**.
3. Choose **All leads** or a saved view.
4. Select the destination: a Slack channel, webhook endpoint, or HeyReach campaign or list.
5. Choose **Auto** or **Manual** delivery. For automatic delivery, review the ICP match threshold.
6. Review the destination and save.

Selecting your personal view shares it with the workspace when the route is saved. A view used by a route cannot be deleted or made personal until you remove the route's dependency.

## Understand automatic delivery

Automatic routes apply to leads entering the audience from that point onward. Saving or editing a route does not send every lead already in the view. Send existing leads manually when needed.

The route threshold controls delivery to that destination. It does not change qualification or pipeline capacity.

## Send manually

Select the intended leads in **Leads**, open **Send to**, and choose the named route. Check the channel, endpoint, campaign, or list before confirming.

A queued result means the request was accepted for delivery. Inspect the result to distinguish queued, delivered, and failed work.

## Pause, resume, or delete

Use the route menu to pause or resume delivery. A route can also pause after repeated failures. Fix the connection or receiving system before resuming.

Deleting a route stops future routing. Leads already sent remain in the receiving system. Disabling or disconnecting the integration can stop all of its routes.


# Slack
Source: https://docs.traxy.ai/integrations/slack

Send lead alerts, replies, and workspace summaries to Slack.

Connect Slack when you want lead alerts and workspace updates in your team's channels.

## Connect and test

1. Open **Integrations** > **Slack** and complete the Slack authorization.
2. In **Settings**, review the connected workspace and default channel.
3. Invite the traxy app to a private channel if it does not appear in the picker.
4. Review the available triggers, lead-reply notifications, daily summary, and message customization.
5. Save the configuration and use **Test trigger**.

The default channel receives the notifications and tests configured for it. Lead routes can use their own channels.

## Route an audience

Open **Routes** and add the lead view, destination channel, and delivery mode. You can create a channel from the channel picker when that action is available.

Follow [Route leads to other tools](/integrations/routes) for automatic delivery and sending existing leads manually.

## Handle lead replies

In **Settings**, use **Post lead replies** to enable notifications. Choose LinkedIn, email, or both, and use the default channel or select another channel.

When **Reply from Slack** is enabled, the notification includes a reply box and **Send on LinkedIn** or **Send email**. Review the recipient and channel before sending. **View conversation** opens the conversation in traxy.

## Review notifications

Use **Settings** to configure repeat-engagement events and daily summaries. Repeat engagement concerns new activity from a qualified lead; it is not another newly delivered lead.

If notifications stop, check the connection, trigger, route state, and channel access. Fix the issue before resuming a paused route. A successful test confirms the test request, not all future deliveries.


# Webhook
Source: https://docs.traxy.ai/integrations/webhook

Send qualified lead events from traxy to your receiving service.

Use Webhook to send signed lead events to your receiving service.

## Prepare the receiver

Create a webhook receiver and copy its HTTPS URL. Make sure the workflow can accept requests outside a temporary test session. Prepare an authentication header only if the receiver requires it.

## Connect and test

1. Open **Integrations** > **Webhook**.
2. Enter a connection name and the HTTPS endpoint.
3. Add the required authentication header, if any, and save the connection.
4. Open **Settings** to review triggers and **Payload & help**.
5. Use **Send test payload** and verify the result at the receiver.
6. Open **Routes** to connect an audience to an endpoint and choose its delivery mode.

Follow [routing guidance](/integrations/routes) for automatic delivery, manual sends, and pause/resume behavior.

## Map and verify events

Use the payload samples in the app to map event metadata and available lead, company, contact, and engagement fields. First-delivery and repeat-engagement events have different purposes.

Requests include **X-Traxy-Signature** and **X-Traxy-Timestamp**. Follow **Payload & help** to verify signatures with the signing secret. If you rotate that secret, update your receiver before relying on later events.

An existing authentication header stays saved when its edit field is empty. Use the explicit removal action when you want to clear it.

## Handle failures

A test sends one immediate request. Lead delivery can retry temporary failures, so make downstream processing safe for repeated events.

Inspect both the delivery result and the receiver. Fix an expired URL, authentication failure, or unavailable workflow before resuming a paused route. Disconnecting stops future delivery through the connection; it does not delete records already received.


# Zapier
Source: https://docs.traxy.ai/integrations/zapier

Send qualified lead events from traxy to your Zap.

Use Zapier to send signed lead events to your Zap.

## Prepare the receiver

Create a webhook receiver and copy its HTTPS URL. Make sure the workflow can accept requests outside a temporary test session. Prepare an authentication header only if the receiver requires it.

## Connect and test

1. Open **Integrations** > **Zapier**.
2. Enter a connection name and the HTTPS endpoint.
3. Add the required authentication header, if any, and save the connection.
4. Open **Settings** to review triggers and **Payload & help**.
5. Use **Send test payload** and verify the result at the receiver.
6. Open **Routes** to connect an audience to an endpoint and choose its delivery mode.

Follow [routing guidance](/integrations/routes) for automatic delivery, manual sends, and pause/resume behavior.

## Map and verify events

Use the payload samples in the app to map event metadata and available lead, company, contact, and engagement fields. First-delivery and repeat-engagement events have different purposes.

Requests include **X-Traxy-Signature** and **X-Traxy-Timestamp**. Follow **Payload & help** to verify signatures with the signing secret. If you rotate that secret, update your receiver before relying on later events.

An existing authentication header stays saved when its edit field is empty. Use the explicit removal action when you want to clear it.

## Handle failures

A test sends one immediate request. Lead delivery can retry temporary failures, so make downstream processing safe for repeated events.

Inspect both the delivery result and the receiver. Fix an expired URL, authentication failure, or unavailable workflow before resuming a paused route. Disconnecting stops future delivery through the connection; it does not delete records already received.


# Review companies
Source: https://docs.traxy.ai/leads/companies

Group leads by company and check Meta ads, website traffic, and matching people.

Open **Leads** and select **Companies** to review the companies in your current view. **People** and **Companies** use the same audience filters.

## Inspect a company

A company row shows its matching people count, best ICP match, latest signal, industry, size, and available research. Expand the row to review its people, or open the company panel.

The panel includes:

* **Overview** for company information.
* **People** for people in the current view and other available people at that company.
* **Ads** for recorded Meta ads and when they were checked.

Choose **Show their people** for selected companies, or open a company’s people count, to return to **People** with a company filter. Clear that filter when you want the broader audience again.

Use **Track company** to follow its public activity. Manage the relationship later under **Targeting** > **Companies**. A tracked company can appear before it has matching people.

## Check Meta ads and traffic

Use **Check Meta ads** above the table to check the companies across the current view. To check only selected companies, use the selection action. You can also check a company from its **Ads** tab.

Checks start immediately. Review the result after **Checking…** finishes. Recently checked companies may reuse their existing results. A missing result or an unchecked company is different from a company with no active ads.

Filter by **Running Meta ads**, **Active Meta ads**, or **Monthly visits** when these conditions help define your audience. The **People** table can also display Meta ads and monthly visits as optional columns.

In a saved view, **Check new companies** checks previously unchecked companies automatically. It uses the saved view’s filters; save filter changes separately.

These research checks are separate from [exporting a Meta Ads audience](/integrations/meta-ads).


# Contact details
Source: https://docs.traxy.ai/leads/contact-details

Find contact data, manage enrichment, and review saved details.

Open a lead to review saved work email, personal email, phone, and profile information before requesting another lookup.

## Find contact details

Choose the lookup action for email, phone, or both. Email lookup is included with eligible plan access. Phone lookup requires the phone add-on or an entitlement that includes it. It applies to leads delivered after phone enrichment was activated. Turning it on does not unlock historical phone lookups. Review the availability shown for the individual lead.

A lookup is not a guarantee that a usable address or number exists. Check the saved result and its status before using it.

Contact lookup does not consume pipeline capacity or make the person a new qualified lead.

## Automatic enrichment

Use **Auto-enrich** in **Leads**, or **Settings** > **Company** > **Lead enrichment**, to manage automatic email lookup. It starts off and applies to leads delivered after you turn it on. Turning it off and on again starts a new boundary.

Use the separate historical email action to look up email for existing leads. Review whether to include leads marked **Done**. Manual email and export lookups do not require you to enable automatic enrichment.

Saved contact details remain available after you disable automatic email or remove the phone add-on, while workspace access permits reading them.

## Manually supplied details

You can edit a lead’s work email, personal email, or phone in the app, or ask trax to save details you provide. Review the proposed value before approving. Manually supplied details are saved as unverified, and enrichment does not overwrite them. Entering a phone number does not require the phone add-on. Clearing a manual value makes that field eligible for lookup again.

Future messages use the updated contact details. Previously delivered integration records are not automatically sent again.

## Export or send contacts

Review the selected fields and destination before exporting or routing leads. Public API and MCP access to contacts requires the appropriate [contact scope](/api-reference/authentication).


# Exports and deleted leads
Source: https://docs.traxy.ai/leads/exports-and-recovery

Export selected lead data and recover deleted leads.

Use exports to take the selected lead data into another workflow. Use deletion only when you want to remove leads from normal workspace views.

## Export leads

1. Open **Leads** and apply the intended view and filters.
2. Select the leads to export. Use the option to select all matching leads when you want the whole filtered result, then review the selected count. **Export** requires a selection.
3. Choose the columns and available enrichment options.
4. Confirm the export and follow its progress.
5. Download the file when the export is ready.

Exporting does not move leads to **Done** unless you explicitly choose that option.

Use **Settings** > **Exports** to review export history. An export that is queued or processing is not ready to download. If it fails, review the reason before retrying.

Deleting a finished export removes its downloadable file and history entry. It does not delete the underlying leads. Active exports cannot be deleted while they are processing.

## Delete and restore leads

Review the confirmation carefully before deleting a selection. Use **Settings** > **Deleted leads** to review recoverable leads and restore those you need.

Deleting or restoring a previously delivered lead does not refund or consume pipeline capacity. If you only want to finish work on a lead, use **Done** instead. If you need to suppress outreach, use [Do not contact](/outreach/do-not-contact).


# Review qualified leads
Source: https://docs.traxy.ai/leads/overview

Understand each lead and choose the next step for your team.

Open **Leads** to review qualified people in your workspace. Start with the lead's role, current company, ICP match, and recorded signal.

## Choose a view

Use the built-in views to distinguish active work, clients, snoozed leads, completed work, and bad fits. Apply filters for the audience you need, then [save a view](/leads/saved-views) if you will reuse it.

Search and filters affect which results you see. Check active filters and the selected workspace when a lead appears to be missing.

## Switch between people and companies

Use **People** to work with individual leads. Use **Companies** to group the audience by company and review its matching people, Meta ads, and website traffic. See [Review companies](/leads/companies).

## Inspect a lead

Open the lead to review its overview, signals, details, and activity. Check the source and date of recorded evidence before referencing it in outreach.

[Contact details](/leads/contact-details) show saved contact information and lookup actions. [Notes and assignments](/leads/team-work) help members coordinate the next step.

## Classify your work

* Use fit feedback to explain whether the lead matches your ICP. For **Bad fit**, complete the reason and choose whether to keep the lead in the list or remove it when prompted.
* Use **Snooze** when you want to return later.
* Use **Done** when the work is complete.
* Use **Client** for an existing customer.

Use **Move to Active Leads** in **Bad fit** to restore a removed lead’s visibility. This preserves the feedback and score.

Moving a lead to **Done** does not change its fit score. Restore it to active work when needed. These actions are separate from [Do not contact](/outreach/do-not-contact).

## Act on an audience

Use the table-header selection control to choose all matching leads, the current page, or the first number of leads in the list’s current order. Check the filters and sort before choosing the first results. Use **Clear selection** to start again.

Select leads for supported bulk actions, [export them](/leads/exports-and-recovery), [send them to an integration](/integrations/routes), or use a saved audience in a [campaign](/campaigns/create). Check the selection and destination before confirming.


# Filter and save audiences
Source: https://docs.traxy.ai/leads/saved-views

Create personal or shared lead views for review, campaigns, and routing.

Use a saved view when you want to return to the same audience without rebuilding its filters.

1. Open **Leads** and choose a built-in or saved view from its menu. When that menu is hidden, use the view picker above the table.
2. Add filters for the people, companies, signals, or workflow state you need.
3. Review the matching leads.
4. Choose **New view** or **Save as new view**, give it a recognizable name, and choose its sharing setting.

A view created from table filters updates as matching leads and their data change. It also keeps your choice of **People** or **Companies**. Table columns and temporary search text are separate from the saved audience.

When you ask trax to save a search that depends on text, topics, or a custom ICP score range, it saves a fixed audience of the leads matched at that time. New matching people do not automatically join that fixed audience. Review the saved result before using it in a campaign or route.

A view saved while a post's lead scope is selected keeps that post scope. Check the post banner before saving or clearing it.

The page heading identifies the open view. A **Filtered** badge indicates changed filters; it does not mean those changes have been saved.

Use the menu beside a saved view to **Edit**, **Duplicate**, or **Delete** it. Shared and personal views appear in separate groups.

## Personal and shared views

Personal views are visible to their creator. Shared views are available to the workspace, and members can update their name and filters. Only the creator can change a shared view back to personal.

Use **Save as new view** or duplicate a view when you want a separate audience. If another member has changed a shared view, reload its current version before applying your edit.

## Check new companies

In a saved view, **Check new companies** automatically checks Meta ads and traffic for companies that have not been checked. The switch saves immediately and uses the view’s saved filters. Save any filter edits separately. Built-in views do not have this switch.

## Use a view elsewhere

Campaigns and integration routes can use shared views. Selecting your personal view for a route shares it when you save the route.

You cannot delete or make a view personal while a campaign or integration route depends on it. Remove that dependency first. Deleting a view does not delete its leads.


# Tags, notes, and assignments
Source: https://docs.traxy.ai/leads/team-work

Coordinate lead review and outreach with other workspace members.

Use workflow fields to make ownership and context clear before members contact the same lead.

## Assign a lead

Choose **Assign** to select an active member, or **Assign to me** to take the next step yourself. You can also assign a selection of leads in bulk.

Assignment identifies who is working on the lead. It does not change qualification or the lead's recorded source.

## Organize with tags

Apply lead tags to group audiences or track your team's process. Use filters to find tagged leads and save that filter as a view.

Lead tags are separate from tags used for tracking profiles. Review the affected leads before deleting or replacing a tag.

## Add a note

Open the lead's notes and record useful context for the workspace. Notes are shared with members. Only the author can edit or delete their note, and deleting a note is permanent.

## Filter your work

Use assignment, tags, notes, status, and feedback filters to build a queue. For example, save a view of active leads assigned to you that still need review.

These workflow changes do not consume pipeline capacity or change qualification scores.


# Do not contact
Source: https://docs.traxy.ai/outreach/do-not-contact

Suppress outreach to people who should not receive further messages.

Use **Settings** > **Do not contact** to review outreach suppression. Choose email or LinkedIn, enter the email address or profile identifier requested by the form, and add the entry.

You can also upload a CSV with `kind,value` columns. Use `EMAIL` for email addresses and `LINKEDIN` for LinkedIn entries. Review the file before uploading it so the type and value match the contact you intend to suppress.

Suppression affects outreach eligibility. Unsubscribe requests and hard bounces also stop active outreach. Check the suppression reason before deciding whether a record should be removed.

## Choose the right action

| Your goal | Use |
| - | - |
| Prevent outreach to a person or contact | **Do not contact** |
| Exclude a company or person from lead results | [Blocklist](/workspace/blocklist) |
| Finish work on a lead | **Done** |
| Return to a lead later | **Snooze** |
| Record that someone does not match your ICP | Fit feedback |

Removing a suppression is not approval to resend an earlier message. Review the person's current sequence and conversation before starting new outreach.


# Use Inbox
Source: https://docs.traxy.ai/outreach/inbox

Read outreach conversations, reply, and manage follow-ups.

Open **Outbound** > **Inbox** to work with outreach conversations, with one conversation per lead.

## Review a conversation

Select a conversation to read its LinkedIn and email messages. Review the sender, channel, and lead details before replying. Use **All**, **Unread**, and **Unresponded** to narrow your queue. Pin, mark read or unread, and archive conversations as needed.

The details pane shows the lead, campaign context, and sequence progress when available. Review the next scheduled step or paused state before making another outreach request.

## Reply

1. Open the conversation and choose an available reply account or channel.
2. Write your reply and add supported attachments if needed.
3. Review the recipient and content.
4. Send and check the result.

An incoming reply stops active sequence outreach. A reply in Inbox is a separate action from approving a campaign's queued message.

## Manage follow-ups

Pause a lead's active enrollment when you need to handle the conversation personally. Resume only when continued outreach is appropriate. A sequence-wide pause still prevents that enrollment from running.

If the composer is unavailable, check the sender connection, lead suppression, and workspace access. See [message troubleshooting](/troubleshooting/campaigns-and-messages).


# Sender accounts
Source: https://docs.traxy.ai/outreach/senders

Connect LinkedIn accounts and mailboxes for outreach in traxy.

Open **Outbound** > **Sender accounts** to connect the accounts your workspace uses for outreach. You can also ask trax to help connect a sender.

## Connect an account

1. Choose **Add sender** and the available account type.
2. Choose the sender name the account belongs to.
3. Complete the connection flow. If sign-in opens in another tab, finish there and return to traxy.
4. Confirm that the account appears as connected.
5. Review its controls before assigning it to outreach.

Accounts are grouped by sender name. A sequence using LinkedIn and email needs a sender name with both connected channels.

## Collect LinkedIn activity

A LinkedIn account can collect activity without sending messages. Configure its activity in **Targeting** > **Intent signals** > **LinkedIn activity**. To use the account for outreach, review its sending state and enable sending when appropriate.

Disconnecting a LinkedIn account can stop both activity collection and outreach using that account. Review the affected uses before confirming.

## Review sending controls

Review the stored limits, active hours, and ramp-up controls available for the account. The app shows the values that apply to that sender; a campaign does not bypass them.

For email, review the sender signature. Sequence and one-off emails include it when present. LinkedIn messages do not use the email signature.

## Reconnect or remove

Reconnect an account when its connection needs attention. Confirm the intended workspace and sender name before completing sign-in.

Before removing a sender, check campaigns and sequences that use it. Removal or disconnection can prevent future messages from being sent. It does not retract messages already delivered.


# Sequences and one-off messages
Source: https://docs.traxy.ai/outreach/sequences

Prepare LinkedIn and email outreach and review each sending action.

Use a sequence for several steps over time. Use a one-off message for a single action to one lead.

## Prepare outreach

Open a lead's **Message** action or ask trax to prepare outreach. Review **To**, **From**, the channel, and the message content.

For a sequence, review each step and the wait before it. A wait can depend on an event such as connection acceptance. Choose sender names with the channels the sequence requires.

A lead can be in only one active sequence at a time. Check existing outreach before enrolling the same person elsewhere.

## Approve sending

For one step, **Send** is the approval. Adding follow-ups creates a sequence; **Activate sequence** approves activation and enrollment for the selected lead.

After activation, inspect the recorded status. **Sending**, **Sent**, **Not sent**, and **May have been sent** have different meanings. An uncertain result must not be treated as a failed send and repeated blindly.

## Pause and resume

Pausing a sequence keeps each lead's position and stops further delivery until it resumes. You can also pause a lead's enrollment from its Inbox conversation. Resuming the whole sequence does not release a lead you paused separately.

Replies, unsubscribe requests, and hard bounces stop active outreach. Sender availability, spacing, and limits can also delay the next step.


# Quickstart
Source: https://docs.traxy.ai/quickstart

Set up your workspace and review your first qualified leads.

Teach traxy who you sell to, review your first qualified leads, and choose how to work with them.

If you received an invitation, follow [Join a workspace](/getting-started/join-a-workspace).

## Before you begin

Have your company website and a description of your target buyers ready. Review the trial or subscription terms in the app before entering payment details.

## Set up your workspace

1. Enter your company website and confirm the company context.
2. Review the generated **Lead criteria** and **Intent signals**. Correct anything that does not describe your buyers or the topics that matter to them.
3. Approve your targeting and review the lead preview. Use fit feedback to explain a mismatch.
4. If the preview is still running or has no results, use the offered option to continue without waiting.
5. Choose the available trial or paid option and complete checkout. Review the confirmation before continuing.

The lead preview helps you evaluate targeting. It does not start your trial by itself.

## Explore your workspace

Choose **Show me around** for a short product tour, or use [Find your way around](/getting-started/navigation). You can replay the tour later from your profile settings.

## Find and review leads

1. Open **trax** and describe who you want to reach. For example: “Discover new leads who are founders discussing their first sales hires.”
2. Review any proposed discovery action and its capacity information before approving.
3. Open the results in **Leads**. Check the person's role, company, ICP match, and recorded signal.
4. Narrow the audience with filters and [save a view](/leads/saved-views) when you want to use it again.

To review people you already have, ask trax to search your existing leads instead.

You can also [track people, posts, or companies](/discovery/tracking) whose audiences are relevant to your workspace.

## Choose your next step

* [Create a campaign](/campaigns/create) to research an audience and prepare outreach.
* [Connect a sender](/outreach/senders) to send through traxy.
* [Route leads to another tool](/integrations/routes) if your team works elsewhere.
* [Troubleshoot missing leads](/troubleshooting/no-qualified-leads-yet) if discovery is not producing results.


# Refund policy
Source: https://docs.traxy.ai/refund-policy

How free trials, billing, cancellations, and refunds work for traxy workspaces.

## Free trial

Every new traxy workspace starts with a 7-day free trial. You can explore the platform during the trial, and you won't be charged until it ends.

## Trial-ending reminder

We'll email you **2 days before your trial ends**. The email tells you the date your trial ends. To avoid being charged, cancel before the trial ends.

## No refunds after the trial

When your trial ends and your paid subscription starts, **all payments are final and non-refundable**.

## Cancelling

You can cancel anytime from **Settings → Billing**. Cancelling stops future charges. Your workspace keeps its access until the end of the billing period you've already paid for.

## Something not right?

If you think something went wrong with your billing, email us at [support@traxy.ai](mailto:support@traxy.ai) and tell us what happened. Screenshots help if you have them. We'll look at your case and get back to you.


# Meetings and outcomes
Source: https://docs.traxy.ai/reporting/meetings

Review meetings attributed to traxy leads and record their outcomes.

Open **Outbound** > **Meetings** to review meetings attributed to your leads. Connect [Google Calendar](/integrations/google-calendar) and select the intended calendars first.

## Review attribution

Open a meeting to inspect its matched lead or company. Attribution depends on available attendee and lead information; connecting a calendar does not mean every event will match.

Use the available date and target filters to review a consistent audience. Check calendar selection and sync state if an expected meeting is missing.

## Record an outcome

Review the meeting and choose the outcome that reflects the conversation. **Active opportunity** records ongoing interest without moving the lead to Clients. **Already a client** and **Closed won** represent different outcomes; choose based on the actual relationship.

## Compare results

Use meeting counts alongside discovery and campaign outcomes. A delivered message is not a reply, and a reply is not a booked meeting.

If you use the API, the [API reference](/api-reference/overview) includes aggregate meeting analytics and an attributed meetings list. Contact permissions control attendee detail access.


# Insights
Source: https://docs.traxy.ai/reporting/performance

Review lead discovery results and audience patterns.

Open **Insights** to review your workspace's lead volume, recent trends, and audience patterns.

## Choose a consistent scope

Review the date range and available filters before comparing numbers. Keep the same workspace and scope when you move between Insights, Tracking, and Leads.

## Review results

Use the lead summary and trend chart to understand how discovery is progressing. Review the available audience breakdowns and top profiles or posts to identify useful sources.

A profile scan, a post engagement, and a delivered qualified lead are different events. Several posts can include the same person, so adding post-level counts may not equal a unique lead total.

## Decide what to change

* If matches are weak, inspect individual leads and refine targeting.
* If volume is low, review source activity and discovery status.
* If capacity is reached, review [your plan and capacity](/workspace/plan-and-capacity).
* To review attributed conversations that became meetings, open [Meetings](/reporting/meetings).

Use underlying lead and signal details to explain a result before changing your configuration.


# Campaign or message not progressing
Source: https://docs.traxy.ai/troubleshooting/campaigns-and-messages

Check approvals, audience eligibility, destinations, and sender status.

Open the campaign and the affected lead to identify the stage that is waiting.

| What you see | What to check |
| - | - |
| Draft or completed test | Review the preview and launch when ready. A test does not send. |
| Awaiting approval | Review the campaign queue and approve the intended messages. |
| No eligible leads | Check saved views, filters, prior outreach, and overlapping campaign priority. |
| Needs a destination | Connect or select the destination shown by the campaign. |
| Paused | Check both the campaign or sequence and the individual lead's enrollment. |
| Waiting to send | Check schedule, sender connection, active hours, limits, and required prior events. |
| Not sent | Inspect the failure before using the offered retry action. |
| May have been sent | Inspect the conversation and recorded result; do not repeat the message blindly. |

## Check suppression and replies

A reply, unsubscribe, hard bounce, or **Do not contact** entry can stop outreach. Removing a suppression does not itself authorize another message.

## Check the destination

For an integration, inspect its route and delivery result. For HeyReach, inspect the destination campaign there as well. A queued lead is not proof of delivery, and delivery into a tool is not proof that outreach was sent.

If the cause is still unclear, contact support with the workspace, campaign, affected action, and approximate time. Do not include API keys or sender credentials.


# Connection and permission issues
Source: https://docs.traxy.ai/troubleshooting/connections

Resolve missing integrations, tools, workspace access, and delivery failures.

## Integration delivery

Check that the connection is enabled, the route is active, and the destination is valid. Run the available test and inspect the receiving system. Fix authentication or endpoint failures before resuming a paused route.

## MCP authorization

If the client has no tools, check that OAuth completed and the connection is enabled. REST keys do not authenticate MCP.

Ask the client to list authorized workspaces. If the required workspace is absent, authorize again and select it. Existing grants do not expand automatically when you join another workspace.

A tool can be missing because its scope was not granted or your role or workspace access no longer permits it. Reconnect only when you need new consent; fix the underlying role or access issue when that is the cause.

## API keys

Check the key's workspace, revocation state, and scopes. Use a bearer header and the public base URL. Keep keys out of query strings and browser code.

Use [API error guidance](/api-reference/pagination-and-errors) to distinguish authentication, access, validation, and rate-limit failures.

## Missing meetings or replies

For meetings, check [calendar selection and sync](/integrations/google-calendar), the date range, and matching attendee information. For replies, check the connected sender and the conversation's channel. A connection test alone does not prove that a particular event has synchronized.


# FAQ
Source: https://docs.traxy.ai/troubleshooting/faq

Answers about qualification, capacity, campaigns, and connected tools.

## What is the difference between the Agent and discovery runs?

**trax** is the workspace chat assistant. **trax** > **Discovery runs** shows discovery history and controls. Searching your existing leads is separate from starting discovery for new people.

## Does a scanned profile count as a new lead?

No. Pipeline capacity counts a person when first delivered as a visible qualified lead in your workspace. Scans and repeated signals are separate.

## Does a filter change qualification?

No. A filter changes the results you see. Update **Lead criteria** or **Intent signals** to change discovery targeting.

## Does fit feedback change the score?

Feedback records your verdict and reasons. It does not directly rewrite the score. Review and save targeting changes separately.

## Can I reuse an audience?

Yes. Save a lead view and share it when members, campaigns, or routes need it. The view stores filters, so its matching people can change over time.

## Does a campaign test send messages?

No. Review the test and launch approval separately. A live campaign can still require message approval depending on its delivery mode.

## Why does a message wait after approval?

Sender availability, schedules, limits, prior steps, replies, and suppression can affect delivery. Inspect the lead's status rather than resubmitting the same request.

## Do integrations send existing leads automatically?

Saving or editing a route does not backfill the audience already in the view. Send those leads manually when appropriate.

## Does MCP use the workspace I last selected in the app?

No. Each scoped call uses its explicit `workspaceId` or the connection's original default. See [MCP workspace selection](/api-reference/mcp/workspaces).

## Where do I find billing and refund terms?

Review **Settings** > **Plan** and **Billing**, the terms shown at checkout, and the [refund policy](/refund-policy).


# No new qualified leads
Source: https://docs.traxy.ai/troubleshooting/no-qualified-leads-yet

Find out whether discovery is waiting, paused, or finding too few matches.

Check the workspace and cause before requesting another run.

## Check the view

Confirm the workspace, lead view, search, score filter, and date filters. A saved view can hide otherwise visible leads. Look in **Done**, **Snooze**, **Clients**, **Bad fit**, or **Deleted leads** when appropriate.

## Check discovery status

Open **trax** > **Discovery runs** and inspect the latest run. A request can be queued, running, finished, or unable to start. A completed run with few matches is different from a run still processing.

## Check capacity and access

Review the pipeline overview. If capacity is reached, new discovery pauses until capacity becomes available. If the workspace is read-only or requires reactivation, restore access through the offered action.

If capacity remains but supply is low, an upgrade is not the first fix. Review targeting and sources.

## Review targeting and sources

Check **Lead criteria** for overly narrow or conflicting requirements. Check **Intent signals** for relevant topics. Confirm tracked profiles are active and have relevant activity.

Inspect any available candidate or lead results. Use concrete mismatch reasons to adjust targeting instead of lowering a display filter and expecting qualification to change.

## Check the destination separately

If leads appear in traxy but not another tool, discovery worked. Review the [integration route](/integrations/routes), connection, and delivery result instead of restarting discovery.


# Agency outreach
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-agencies

Keep each service audience and campaign focused on a clear offer.

Choose one service and buyer segment for a campaign. Describe the company context, target roles, and signals that make the service relevant.

Save a shared view for the audience. Ask trax to prepare a campaign that uses a supported observation and a concrete next step. Review sample results before approving launch.

Use assignments and shared notes so members can see who is handling each lead. Keep separate client or business contexts in the appropriate workspace and verify the workspace before making changes.

Follow [Members and workspaces](/workspace/team) and [Create a campaign](/campaigns/create) for the product steps.


# Content-led outreach
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-content-led

Review people engaging with relevant content and prepare a campaign.

Track your relevant profiles or add a specific post in **Tracking**. Inspect the qualified leads and the actual interaction behind each result.

Save a view for the audience you want to work with. Ask trax to draft a campaign that responds to the topic and offers a useful next step. Review the test for unsupported assumptions before launch.

A reaction alone does not prove that a person read the whole post or wants to buy. Keep the wording proportional to the evidence.

After launch, review replies and meetings rather than treating engagement volume as a sales outcome. Follow [Create a campaign](/campaigns/create) for setup.


# Event-related outreach
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-events

Use relevant public event context without assuming attendance or interest.

If a public post or interaction relates to an event, inspect the evidence and qualified lead before referencing it.

Add a relevant LinkedIn post through **Tracking** and review its audience. Do not treat a post interaction as proof of event registration, attendance, or consent to unrelated follow-up.

Save the audience, describe the event context to the Agent, and test the campaign. Check that each message uses only supported facts and that the timing still makes sense before launch.

Review replies in [Inbox](/outreach/inbox) and record actual outcomes in [Meetings](/reporting/meetings).


# SaaS outreach
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-saas

Build a campaign around a defined software buyer and relevant evidence.

Define the roles and company characteristics that match your software. Choose signals tied to the problem it solves, then inspect the resulting qualified leads.

Save an audience view and ask trax to research the facts needed for your offer. In the campaign test, check whether each company-specific claim has support. Remove claims about tooling, budget, or urgency that the research does not establish.

Review the sender, message steps, and delivery mode before launch. Use tags and assignments to coordinate follow-up across members.

Start with [Lead criteria](/discovery/lead-criteria) and [Review and launch](/campaigns/review-and-launch).


# Outbound from qualified signals
Source: https://docs.traxy.ai/using-traxy/outbound-to-signal-based-leads

Build outreach from verified lead context.

Start with a qualified audience and an observation you can support from the lead's recorded evidence.

1. Review **Lead criteria** and **Intent signals**.
2. Filter leads by fit and relevant signal context.
3. Save the audience as a shared view.
4. Ask trax to prepare a campaign using that view and your offer.
5. Test the plan and inspect the facts and messages.
6. Review the launch dialog and delivery mode before approving.
7. Handle responses in Inbox or the chosen destination and record meeting outcomes.

Reference only facts the source supports. Do not infer a person's budget, intent, or dissatisfaction from a generic interaction. If the evidence is too weak, change the message or skip the lead.

Use [Review and launch](/campaigns/review-and-launch) for the product steps and [Intent signals](/discovery/signals) for signal labels.


# Use signals in outreach
Source: https://docs.traxy.ai/using-traxy/signal-cheat-sheet

Choose a message angle that matches the evidence.

Read the lead's source and date before choosing an angle.

| Evidence | A useful approach | Avoid |
| - | - | - |
| A relevant comment or question | Respond to the specific problem raised. | Claiming an intent to purchase. |
| A relevant post by the person | Connect your offer to the topic they discussed. | Inventing a current project or budget. |
| Engagement with someone else's post | Use the topic as context when the interaction supports it. | Claiming they endorse every idea in the post. |
| Company or role fit without a strong signal | Use a factual role-based introduction. | Inventing an interaction for personalization. |

Signal labels and ICP match are separate. Review [Intent signals](/discovery/signals), then test a small campaign sample before approving outreach.


# Account and security
Source: https://docs.traxy.ai/workspace/account

Manage your profile, sign-in settings, and workspace context.

Open **Settings** > **Profile** to review your personal information. Use **Security** for the sign-in controls available to your account.

## Replay the product tour

On a desktop-sized screen, choose **Replay tour** under **Product tour** in your profile settings. It opens a walkthrough of the areas available to you. You can also start it from **Product tour** in your account menu.

## Keep access current

Use the email address and sign-in method associated with your account. If password controls are unavailable for your sign-in method, follow the recovery options offered by that provider.

When an invitation or verification link expires, request a fresh link rather than repeatedly opening the expired one.

## Check the workspace

Before changing shared settings, confirm the workspace name. Switching workspaces changes the leads and configuration you are working with. It does not move leads or campaigns between workspaces.

Ask an admin to review your role if an action is unavailable. For connected tools, review their authorization separately; removing a tool connection and changing a member's workspace role are different actions.


# Billing and subscriptions
Source: https://docs.traxy.ai/workspace/billing

Manage payment details, invoices, subscription changes, and cancellation.

Open **Settings** > **Billing** to review payment information and billing history. Use **Settings** > **Plan** for the plan and available changes.

Billing actions require the appropriate workspace permission. Other members may have read-only access to billing information.

## Trial and checkout

Review the trial duration, included access, payment method requirement, and conversion terms displayed at checkout. The onboarding lead preview is separate from the trial.

After checkout, wait for the app to confirm access. A checkout redirect alone is not confirmation that a pending payment completed.

## Change or cancel a subscription

Choose the available plan, interval, add-on, cancellation, or pause action. Review the amount due, effective date, and access changes before confirming. Check the result when you return from any payment authorization step.

A scheduled change does not necessarily apply immediately. The app shows when it takes effect and whether you can keep the current plan.

## Read-only access

An ended trial, ended subscription, or paused subscription can leave the workspace read-only. Existing information may remain available while actions that change data or start work are disabled. Use the offered billing action to restore access.

See the [refund policy](/refund-policy) for the published refund terms. For a billing issue, contact [support](mailto:support@traxy.ai) with the workspace name and the issue; do not include payment credentials.


# Blocklist
Source: https://docs.traxy.ai/workspace/blocklist

Exclude companies or people from your workspace's lead results.

Use **Settings** > **Blocklist** to exclude companies by domain or people by LinkedIn profile. Choose **Companies** or **People** before adding an entry or uploading a CSV.

## Block a company

1. Add the company domain using the blocklist action.
2. Review the normalized domain.
3. Confirm the exclusion.

You can also start a domain exclusion from a company's hover card in **Leads**. Review the company carefully so you do not exclude an unrelated domain.

## Block a person

Open **People**, choose **Add people**, and enter the person's LinkedIn profile URL. Review the profile before confirming. For a CSV upload, use the format shown for the selected blocklist type.

## Review exclusions

Blocklisted people and people at blocked companies are excluded from normal lead results. They are not moved to deleted leads. Removing an entry lets otherwise eligible leads appear again and allows future discovery to evaluate them. It does not guarantee new leads or replay past discovery.

Lead CSV exports do not use the blocklist as an exclusion rule. Review the export audience separately when you need to exclude these contacts from a file.

Blocklist is different from [Do not contact](/outreach/do-not-contact). Use outreach suppression when the goal is to stop messages to a particular person or contact.


# Plan and pipeline capacity
Source: https://docs.traxy.ai/workspace/plan-and-capacity

Understand how qualified leads use your workspace capacity.

Open **Settings** > **Plan** to review your plan and included features. Open the capacity indicator in the navigation to view **Manage lead capacity**, including usage and the current period.

## What counts

A person uses capacity once, when first delivered as a visible qualified lead in your workspace. Finding that person again, recording another signal, enriching contact details, exporting, deleting, or restoring them does not count them again.

All lead-discovery sources share the same workspace capacity. Candidate and scan counts are not charges for delivered leads.

## When capacity is reached

Discovery of new people pauses. Monitoring, signals, and enrichment for delivered leads can continue while access permits them.

An upgrade, add-on leads, or the next capacity period can resume discovery. Do not expect a backlog of all people encountered at capacity to arrive automatically afterward.

## Review periods and changes

The app shows the period, reset date, and available plan actions. Capacity periods reset monthly for paid plans, including annual billing. Unused capacity does not roll over.

Review the confirmation for when a plan or add-on change takes effect and any amount due today. Upgrades and reductions can have different effective dates.

## Contact data and campaign access

Email lookup, phone enrichment, and campaign availability have their own entitlement rules. Review the features shown for your workspace. Contact enrichment does not use pipeline capacity.

If discovery reports low supply while capacity remains, refine targeting or add useful sources. Buying more capacity does not solve a lack of matching people.


# Members and workspaces
Source: https://docs.traxy.ai/workspace/team

Manage invitations, roles, and shared workspace context.

Use the workspace switcher to choose the workspace you intend to work in. Leads, targeting, campaigns, and integrations belong to that workspace.

## Invite members

An admin can invite members through the sidebar invitation action or **Settings** > **Team**. Review the email address and role before sending the invitation.

Use the team screen to inspect invitations and active members. Change or remove access when responsibilities change.

## Understand permissions

Members with product access can work with shared leads and targeting. Billing changes and API-key management require the appropriate billing or admin permission. The app disables actions your current role cannot perform.

A connected MCP client also checks the permissions granted during authorization and your current workspace role. Its permissions are documented [separately](/api-reference/authentication).

## Create another workspace

Use the workspace menu when you need separate targeting and lead data. Additional-workspace eligibility depends on paid access. If you are in a trial, review the offered options to finish it or activate paid access before continuing.

## Keep company context accurate

Open **Settings** > **Company** to review company and product information. Use **Lead criteria** and **Intent signals** for targeting changes rather than creating another workspace for every small adjustment.