# Account Health & Credits: Blocklists, Enrichment & Usage
Source: https://docs.traxy.ai/account-health-and-credits-blocklists-enrichment-and-usage
Keep your leads relevant and your credits working for you.
A clean traxy account starts with knowing who not to track and ends with knowing exactly where your credits are going. This walkthrough covers blocklisting domains you don't want signals from, fine-tuning enrichment so you're not wasting credits on low-fit leads, and understanding how credit usage and plans work.
## Keep your leads clean
Once your leads list is clean, the next thing to dial in is how far your credits stretch — which comes down to your enrichment settings and which plan tier you're on.
## Understand credits & plans
Not every lead deserves your attention — or your credits. Here's how to keep both in check:
* Blocklist domains you don't want signals from, so they never show up as leads in the first place
* Snooze a lead temporarily or mark it as a client to keep it out of your active pipeline
* Use advanced filters and auto-enrich by email, phone, or both, so enrichment matches how you'll actually reach out
* Set a minimum ICP score before a lead gets enriched, so credits go to your best-fit leads first
* Credit usage counts up as you qualify leads — one qualification uses one credit — and you can upgrade across tiers from 15K to 100K as you grow
Clean inputs, smart spend — that's how you get the most out of every credit.
# Define your ICP
Source: https://docs.traxy.ai/getting-started/define-your-icp
Use ICP criteria to decide which people and companies count as qualified leads in traxy.
Your ICP decides who counts as a qualified lead in traxy. A narrow ICP usually improves precision. A broader ICP usually increases volume. Revisit it whenever your target market changes.
## Where to update your ICP
* During onboarding, after traxy prepares a Signal Brief from your company website.
* Later in **ICP Configuration** from the main app navigation.
## People criteria
Use people criteria to describe the individual you want traxy to prioritize.
* **Job Titles** help define seniority or function.
* **Departments** help narrow the team you want to reach.
* **Seniority Level** helps distinguish decision-makers and individual contributors.
* **Locations** help limit results to the regions that matter to you.
## Company criteria
Use company criteria to describe the type of company you want to target.
* **Company Size**
* **Industries**
* **Revenue**
* **Funding**
* **Keywords & Niches**
These fields work together. For example, broad industries with narrow keywords can be more useful than a long list of overlapping industries.
## Build a better ICP
1. Start with the fewest signals that clearly define a fit.
2. Use terms your buyers would use about themselves or their companies.
3. Remove broad terms if low-fit leads keep appearing.
4. Broaden one field at a time if you are seeing engagement but not enough qualified leads.
During onboarding, review all three ICP areas before you continue:
* people criteria
* company criteria
* keywords
After onboarding, Agent, Post Signals, and Watchlist use your active ICP when they decide which people should become qualified leads.
Use **Mark as good fit** and **Mark as bad fit** in Leads to add reasons and notes. This feedback helps traxy improve future qualification.
Save changes, watch your dashboard, leads, and post-level results for a short period, then adjust one variable at a time. That makes it easier to see what changed lead quality.
## When to update your ICP
Update your ICP when:
* your team changes who it wants to target
* you are getting too many low-fit leads
* you are seeing real engagement but very few qualified leads
* you launch into a new market, region, or segment
# Join a workspace
Source: https://docs.traxy.ai/getting-started/join-a-workspace
Accept an invite, join the right workspace, and start working in traxy.
Use this page when someone on your team invites you into an existing traxy workspace.
## What to expect
When an admin invites you, traxy sends an invite link tied to that workspace.
Before you accept, the invite stays pending. If it expires, is revoked, or was sent to the wrong address, an admin can send a new one.
## Join a workspace
1. Open the invite link from your email or shared invite message.
2. Sign in, or create your account, with the same email address that received the invite.
3. If traxy asks you to confirm your email before the invite can be accepted, finish that step first.
4. Review the workspace name and your role before you continue.
5. Accept the invite to add the workspace to your account.
6. Use the workspace switcher if you already belong to more than one workspace.
Invited members usually have a shorter onboarding flow than someone creating a workspace. Follow the steps traxy shows for your invite and role.
## What happens after you join
Each workspace keeps its own:
* ICP configuration
* leads
* watchlist
* integrations
* billing and usage settings
Your role controls what you can change inside that workspace.
* **Owner** has full workspace control.
* **Admin** can manage key workspace settings and members.
* **Member** works inside the workspace without full admin access.
## If you cannot join
Check these first:
* You are signing in with the invited email address.
* The invite link is still valid.
* The workspace admin has not revoked and reissued the invite.
* You finished any required email verification.
If the invite still does not work, ask an admin to resend it.
# ICP & Signals: Define & Fine Tune
Source: https://docs.traxy.ai/icp-and-signals-define-and-fine-tune
Define your ICP and tune the buying signals that qualify a lead.
**Learn how to fine-tune your ICP and buying signals in traxy so the leads coming in actually match who you want to reach.**
You'll see how to review your first leads to spot targeting gaps, define the roles, locations, and company criteria that matter, and set the buyer pains and buying triggers that shape which signals count as intent.
This covers how to define and refine your ICP, start to finish:
* **Define your ICP** — set the roles, locations, and company criteria you're targeting, plus any exclusions.
* **Company and product context** — give traxy the context it needs to judge fit.
* **Define buying signals** — set the buyer pains and buying triggers that count as real intent.
* **Refine ICP match** — use lead feedback to dial in your match threshold over time.
* **Research-led feedback** — use Claude MCP and Store Leads to research leads and give more specific feedback.
By the end, you'll have an ICP and signal setup that keeps the leads coming in relevant — and a feedback loop for tightening it further as you see more results.
# Home
Source: https://docs.traxy.ai/index
Turn LinkedIn engagement into qualified pipeline with traxy.ai
traxy helps you turn LinkedIn engagement into qualified pipeline by matching engagement against your ICP. Use these docs to set up your workspace, review qualified leads, monitor important profiles, and route leads into the tools your team already uses.
Go from signup to your first qualified leads.
Tell traxy which people and companies count as a fit.
Search, filter, review, and route qualified leads.
Scan matching profiles and save qualified leads within a daily budget.
Connect the API, Claude, Codex, or a delivery and audience integration.
## Core product areas
Monitor lead volume, threshold-based results, and top-performing posts.
Control automated profile scans, budgets, and run history.
Search for profiles by ICP, filters, and recent engagement.
Define who counts as a fit and improve lead quality over time.
Search, filter, review, enrich, and route qualified leads.
Search posts, qualify post URLs, and find leads from specific posts.
Monitor competitor, teammate, influencer, investor, and custom profiles.
Manage members, roles, invites, and workspace access.
Manage your subscription, credits, payment methods, and invoices.
Diagnose setup, ICP, credit, and lead-quality issues.
## Start here
1. Join or create a workspace, then complete the [quickstart](/quickstart).
2. Review or update your [ICP](/getting-started/define-your-icp).
3. Let traxy finish the onboarding lead preview, then start the Standard Pro Trial.
4. Open [Dashboard](/using-traxy/dashboard), [Agent](/using-traxy/agent), [Leads](/using-traxy/leads), and [Post Signals](/using-traxy/content-calendar).
5. Open [Watchlist](/using-traxy/watchlist) to monitor important LinkedIn profiles.
6. Use [Lead Searcher](/using-traxy/lead-searcher) when you want to explore a specific ICP or segment.
7. Configure [Integrations](/using-traxy/integrations) when you are ready to route data downstream, send leads to your CRM or outbound tools, or build ad audiences.
Your onboarding first run is meant to give you early signal quickly. If volume stays low after it completes, widen your ICP before you assume something is broken.
# Get to Know traxy
Source: https://docs.traxy.ai/product-tour-get-to-know-traxy
A quick guide of what traxy does and how to get the most out of it.
**This video is a full walkthrough of traxy from the moment you log in — how your dashboard reflects your ICP match, how the Agent finds and scores leads, and how everything ties back into the tools your team already uses.**
If you're new to traxy or just want a refresher on how the pieces fit together, this is the one to watch.
This is a walkthrough of the core traxy workflow, start to finish:
* **Dashboard** — a snapshot of your account's activity and how leads match your ICP.
* **ICP & buying signals** — how to define who you're targeting and what signals count as intent.
* **Agent & watchlist** — how the Agent runs against your budget, and how to track specific profiles and posts.
* **Leads** — where qualified leads land, ready to review and act on.
* **Integrations** — connecting traxy to Slack, MCP, and other outbound tools your team uses.
By the end, you'll have a clear picture of how traxy moves a lead from signal to outreach and where to go next to fine-tune any part of that flow for your own team.
# Quickstart
Source: https://docs.traxy.ai/quickstart
A quick guide of what traxy does and how to get the most out of it.
From finding your best leads to fine-tuning it around your ICP. Adam, traxy's Head of Go-to-Market, kicks things off with a quick overview — then the rest of this guide goes step by step: qualifying leads and signals, configuring your ICP, running the agent and watchlist, and keeping your account clean as you scale.
***
## 6 steps to get traxy fully set up
A quick tour of what traxy does and how it works.
Define your ICP and tune the buying signals that qualify a lead.
See how traxy finds and qualifies your warmest, highest-intent leads.
Set up your watchlist and let the Agent work your strategy.
Invite your team for free and spin up a new workspace for a different ICP.
Blocklist domains, fine-tune enrichment, and see how credit usage works.
# 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.
# Team & Workspaces: Invite Teammates & Add New ICPs
Source: https://docs.traxy.ai/team-and-workspaces-invite-teammates-and-add-new-icps
Bring your team in for free, then spin up a new workspace whenever you take on a different ICP.
traxy doesn't charge for extra seats, so there's no reason to keep your team locked out. This walkthrough covers inviting teammates with the right role, plus how to set up a brand new workspace anytime you're chasing a different ICP — whether that's a client's site or a new offer of your own.
## Invite your team
Once your team's in, the next thing worth setting up is a workspace for each ICP you're chasing — so a client site or a new offer doesn't get lumped in with the rest.
## Add a new workspace
Growing your team and juggling multiple ICPs shouldn't slow you down — here's what to set up:
* Invite unlimited teammates for free from Settings → Profiles & Users, assigning each one as a Member or Admin
* Their invite goes out as a pending email — copy the link, re-invite, or remove access anytime
* Spin up a new workspace whenever you take on a different ICP, either running full onboarding for a new site or skipping straight to setting the ICP and signal brief yourself
* Each new workspace gets its own 7-day trial, and you can switch between workspaces anytime
More hands, more workspaces — same traxy account, zero extra cost.
# FAQ
Source: https://docs.traxy.ai/troubleshooting/faq
Answers to common public user questions about traxy.
A qualified lead is a person whose LinkedIn engagement or Agent profile matches your workspace ICP at or above the minimum match.
Select the entire list of leads on the top left selectable icon, or just select the ones that you want to export, and then click export on the bottom of the list.
Go to your [Settings](https://app.traxy.ai/settings) > [Exports](https://app.traxy.ai/settings/exports) and click the download icon to the right for the list you will want to download.
Qualified engagement is engagement from people who meet your workspace fit criteria closely enough to matter for lead qualification.
Most qualification credits settle when traxy saves a successful result. Agent is different: after the trial allowance, it uses credits for each unique profile scanned in the billing window, even when the person does not become a qualified lead.
No. Credits will **only** be consumed if there is a phone number or email found.
You can update your ICP during onboarding or later in **ICP Configuration** from the main app navigation.
Slack notifications stay disabled until you select a channel and enable the trigger. If you chose a private channel and it does not appear in the channel list, invite the traxy Slack app to that channel with `/invite @traxy` before you test it.
Webhook sends qualified lead events from traxy to your endpoint so another system can receive and act on them.
Zapier, Clay, and n8n use the same signed webhook delivery model, but each has its own integration page, connection state, and manual send option.
Ordinal uses a dedicated traxy integration key. Generate the key from **Integrations** > **Ordinal**, then paste it into the traxy integration inside Ordinal.
Auto-send only applies to leads that qualify after it is enabled. Use manual delivery from the leads table if you want to send existing leads.
No. Connect from **Integrations** > **Claude** or **Integrations** > **Codex**. Both use OAuth. API keys are for direct REST access.
Repeat engagement alerts only send when the integration trigger, auto-send, and **Send repeat engagement from qualified leads** are all enabled.
Yes. Each workspace can configure Webhook, Zapier, Clay, and n8n separately.
We qualify the most recent 5. To qualify older post you would have to manually select them in [Post Signals](https://app.traxy.ai/post-signals).
The post may have no engagement, qualification data may still be refreshing, or your workspace may not have enough credits for the action.
New credit-funded qualification, enrichment, and Agent work cannot start. Existing saved leads remain available. Work can resume after the monthly credit window resets or the plan changes.
Yes. If you belong to more than one workspace, use the workspace switcher in the sidebar to move between them.
Open **Settings** > **Blocklist** to add or remove company domains that should not appear as future leads.
Open **Settings** > **Billing** for subscription tasks, credit usage, payment methods, invoices, and plan changes.
A workspace owner or admin should open **Settings** > **Billing** > **Manage Subscription**, select **Cancel Plan**, and complete the cancellation in Stripe. Review the effective date before confirming. See [Cancel a subscription](/using-traxy/billing-and-credits#cancel-a-subscription).
All traxy workspaces start with a 7-day free trial, and you won't be charged until it ends. Once your trial ends and your paid subscription starts, all payments are final and non-refundable. See our full [Refund Policy](/troubleshooting/refund-policy) for details.
Cancel anytime before your trial ends from Settings > Billing. We also email you 2 days before your trial ends as a reminder.
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.
# No qualified leads yet
Source: https://docs.traxy.ai/troubleshooting/no-qualified-leads-yet
Troubleshoot low lead volume or missing qualified leads in traxy.
If you are seeing little or no qualified lead activity, work through these checks in order.
## 1. Check whether processing is still running
After onboarding, traxy needs time to process recent activity and match it against your ICP.
Start with:
* **Dashboard** for overall progress
* **Agent** for automated profile-scan status
* **Leads** for newly added people
* **Post Signals** for post-level review
* **Watchlist** for monitored profile status
If you recently changed your ICP or qualified a post, give the workspace time to refresh.
## 2. Review your ICP
An ICP that is too narrow is the most common reason for low lead volume.
Review:
* people criteria such as job titles, departments, seniority, and locations
* company criteria such as size, industry, revenue, funding, and keywords
If engagement exists but qualified leads do not, broaden one field at a time and monitor the results.
## 3. Check your fit threshold
If your workspace uses a high ICP match threshold, borderline matches may never become qualified leads.
If your role allows it, reduce the threshold slightly and watch whether lead volume improves without hurting quality.
## 4. Check source activity
Low posting volume or low engagement can also limit lead discovery.
Look for these dashboard patterns:
* no posts analyzed
* low engagement
* engagement without qualified leads
Use Post Signals to search tracked posts, widen the time range, or qualify a LinkedIn post URL directly when appropriate.
You can also use the sidebar lead-discovery actions to track a profile, score a LinkedIn URL, or pick from recent activity.
## 5. Check Agent and Watchlist
Open **Agent** and check whether it is active, paused, blocked by credits, or still running.
If Agent is paused, check the daily credit budget, next run, trial status, and plan usage.
If you rely on Watchlist, confirm at least one profile is active in **Monitor**. The free initial discovery and required trailing-five monitoring show their state in Watchlist and Post Signals.
## 6. Check credits
Trial workspaces use the trial limits shown in the app. Paid workspaces use the credits and billing rules shown in **Billing & Plans**.
If credits are exhausted or billing is paused, lead discovery actions may be limited.
Open [Billing & Plans](/using-traxy/billing-and-credits) and confirm the workspace has credits and active plan access.
## 7. Confirm your downstream setup
If leads exist in traxy but are not reaching Slack or your Webhook, the issue may be in delivery rather than qualification.
Check:
* Slack channel selection
* Slack app access to private channels
* trigger status
* Webhook endpoint configuration
* test delivery results
If you are getting engagement but not enough qualified leads, start by widening your ICP before you change your publishing strategy.
# Agent
Source: https://docs.traxy.ai/using-traxy/agent
Run automated lead discovery, set a daily credit budget, and review Agent history.
Use Agent when you want traxy to find people that match your approved ICP without choosing each LinkedIn post or profile yourself.
## Check Agent status
The status switch shows whether Agent is active or paused. Use it to pause or resume scheduled work.
Agent scans every hour while it is active and eligible to run. The **Today** card shows:
* leads found today
* the next scheduled run
* the daily credit budget
* the current rate per profile
Use **Run now** to request a run immediately. A run still follows your current access, allowance, and credit rules.
## Set the daily budget
Use the daily budget control to decide how many credits Agent may use each day.
The change saves when you commit the control. There is no separate save button.
A larger budget lets Agent examine more profiles. It does not guarantee a fixed number of qualified leads because qualification depends on your ICP and the profiles examined.
The Standard Pro Trial includes the Agent allowance shown in the app. After that allowance, Agent uses credits for each unique profile it scans during the billing period.
## Review targeting
**What it looks for** summarizes the active ICP Agent uses.
Open **ICP Configuration** when you want to change job titles, departments, seniority, locations, company criteria, keywords, or the company summary. Agent does not keep a separate targeting configuration.
## Review run history
Use the calendar and run list to inspect recent work. A run can show:
* profiles scanned
* leads saved
* credits used
* run status
Open a run when candidate details are available. If a run cannot start, review the status message, daily budget, current credits, and trial or plan access.
## Agent and Watchlist
Agent and Watchlist use different discovery paths:
* Agent scans matching profiles based on your ICP and budget.
* Watchlist monitors selected LinkedIn profiles and qualifies people who engage with their posts.
Use both when you want broad discovery and account-specific signals.
# Billing & Plans
Source: https://docs.traxy.ai/using-traxy/billing-and-credits
Manage your traxy subscription, credits, payment methods, and billing history.
Use **Settings** > **Billing** to review your subscription and credit activity.
Owners and admins can make billing changes. Other members can review the usage information available to them.
## Use the billing tabs
* **Overview** shows the current plan, credit balance, billing dates, and Watchlist access.
* **Credit Usage** shows the credit ledger for the current billing window.
* **Payment Methods** manages saved payment methods.
* **Billing History** shows invoices and payment history.
* **Manage Subscription** handles plan and billing interval changes and provides cancellation controls when available.
Use the plan and checkout screens in your workspace for current pricing and included credits.
## Understand the Standard Pro Trial
New workspaces can start a card-required seven-day Standard Pro Trial after the onboarding lead preview.
The trial includes the Agent allowance and product access shown in the app. There is no permanent free plan. If a trial or paid subscription ends, traxy keeps the workspace data needed for reactivation.
## Understand credit windows
Included credits reset monthly on the workspace billing anniversary in UTC. **Overview** shows the current window and next reset.
traxy enforces the available balance before new credit-funded work starts. It does not create unpaid overage debt.
When no credits remain:
* new manual post qualification cannot reserve credits
* scheduled qualification pauses
* new enrichment cannot start
* Agent work that requires credits cannot start
* existing saved leads and workspace data remain available
## Understand credit charges
Most credits settle only after traxy saves a successful result.
* Qualification uses 1 credit for each unique billable profile in the current billing window.
* Email enrichment uses 3 credits when a new email is found and saved.
* Phone enrichment uses 5 credits when a new phone number is found and saved.
Agent is the exception. After the Standard Pro Trial allowance, Agent uses credits for each unique profile it scans in the billing window, even if the profile does not become a qualified lead.
traxy deduplicates the same person within the relevant billing window. Review **Credit Usage** for the final ledger.
## Review credit usage
Open **Credit Usage** to:
* review qualification, Agent, and enrichment charges
* search by the available lead, person, or post details
* filter by activity, credit type, and date
* compare activity within the current billing window
## Manage your subscription
Use **Manage Subscription** to review the plan actions available to your workspace.
Depending on the current subscription, you can:
* change plan
* change billing interval
* open Stripe's billing portal
* cancel the subscription
* review a scheduled change
## Cancel a subscription
1. Open **Settings** > **Billing**.
2. Select **Manage Subscription**.
3. Find the cancellation panel.
4. Click **Cancel Plan**.
5. Complete the cancellation in Stripe.
6. Review the effective date before you confirm.
The billing status may take a moment to refresh after you return to traxy.
If **Cancel Plan** is not available, ask a workspace owner or admin to review the subscription or contact support.
## Watchlist and members
Watchlist profiles and workspace members are unlimited. Qualification still follows the workspace credit balance.
A plan can still apply separate limits to other resources, such as competitor companies. The app shows those limits where they apply.
Use the billing screen in your workspace as the source of truth for your plan, included credits, renewal date, and available subscription actions.
# Blocklist
Source: https://docs.traxy.ai/using-traxy/blocklist
Exclude company domains from future qualified leads in traxy.
Use Blocklist when you want traxy to exclude future leads from specific companies.
## Add a company domain
1. Open **Settings** > **Blocklist**.
2. Enter the company domain you want to exclude.
3. Save the domain.
You can also add a company to the Blocklist from a company hover card in **Leads**.
## What happens after you add a domain
After you add a domain, future leads from that company stop appearing in your workspace.
Use this for companies that are already customers, competitors, internal entities, or accounts your team does not want in the active lead flow.
## Manage blocked domains
Use **Settings** > **Blocklist** to search, review, and remove blocked domains.
If you remove a domain, future lead discovery can include that company again when its engagement matches your ICP.
# Connect Claude to traxy
Source: https://docs.traxy.ai/using-traxy/connect-claude
traxy connects to Claude through a custom MCP (Model Context Protocol) connector. No API key is required — the connection uses secure browser OAuth.
### 1 minute guide on how to connect traxy x Claude!
In the traxy sidebar, go to **Integrations**, find the **Claude** card, and click **Configure**, or simply click [**here**](https://app.traxy.ai/integrations/claude). On the integration page, make sure the **App & browser** tab is selected (use the **Terminal** tab instead if you're connecting Claude Code from the command line).
Click **Copy MCP URL** to copy the connector URL:
```text theme={null}
https://api.traxy.ai/api/v1/mcp
```
You'll paste this into Claude in the next step.
In Claude (web or desktop), click your profile menu in the bottom left and select **Settings**.
Go to **Connectors** in the left sidebar, then click **Add** → **Add custom connector**.
In the **Add custom connector** dialog:
1. Name the connector `traxy.ai` (shown in your connectors list).
2. Paste the MCP URL you copied — `https://api.traxy.ai/api/v1/mcp` — into the **Remote MCP server URL** field.
3. Leave **Advanced settings** (OAuth Client ID/Secret) blank — they're optional and not required for traxy.
4. Click **Add**.
Claude will show "You are not connected to traxy.ai yet." Click **Connect**.
You'll be redirected to traxy's authorization page:
* Select the **Workspace** you want Claude to access.
* Review the **Requested access** scopes (leads, analytics, ICP & Signal Brief, watchlist, integrations, agent tools, and more).
* Click **Approve**.
If your traxy account belongs to a Team or Enterprise plan, an organization owner may need to approve the connector.
You'll see a **Connected** confirmation screen. Click **Open desktop app** if prompted, or simply return to Claude — you can close the browser tab.
Back in Claude's **Connectors** settings, `traxy.ai` now appears as connected, with a full list of available tools (e.g. *Get account report*, *Get active ICP*, *Get analytics dashboard*). By default, tool permissions are set to **Needs approval**, so Claude will confirm with you before calling a tool.
## Next steps
Once connected, you can ask Claude things like *"What's my traxy lead pipeline look like this week?"* or *"Pull my top-performing posts from traxy"* — Claude will call the relevant traxy tools directly.
To disconnect at any time, go to **Settings → Connectors → traxy.ai** and click **Disconnect**.
# Connect Claude, traxy, and HeyReach
Source: https://docs.traxy.ai/using-traxy/connect-claude-to-hey-reach
This workflow connects traxy to HeyReach so qualified leads flow straight into your campaigns, then connects HeyReach to Claude so you can manage that pipeline conversationally.
In HeyReach, go to **Settings → Integrations**, then select **HeyReach API**.
Click **New API key** to generate one (this invalidates any previous key), then copy it.
Back in traxy, go to **Integrations → HeyReach**.
1. Paste your HeyReach API key into the **API connection** field and click **Connect**.
2. Under **Destination**, set the **Destination type** to `Campaign` and select (or create) the campaign traxy should send leads to.
3. Under **Delivery**, choose **Manual** (send leads yourself from the Leads table) or **Auto** (send every new lead above your ICP match threshold automatically).
4. Click **Save settings**.
Still in HeyReach, go to **Settings → Integrations → HeyReach MCP Server**.
Copy the **MCP Connection URL** (it already includes your MCP key, e.g. `https://mcp.heyreach.io/mcp?xMcpKey=...`).
In Claude, open **Settings → Connectors → Add → Add custom connector**.
1. Name it `heyreach`.
2. Paste the MCP Connection URL into the **Remote MCP server URL** field.
3. Leave OAuth fields blank — the key is already in the URL.
4. Click **Add**.
Claude will show "You are not connected to heyreach yet." Click **Connect**. Since the key is embedded in the URL, the connection completes immediately — no separate authorization screen.
With traxy delivering leads into your HeyReach campaign and HeyReach connected to Claude, open a new chat and run the following prompt:
```text theme={null}
Select the best [X] leads from Traxy for a HeyReach LinkedIn outreach campaign and set up personalized messaging for them.
Lead selection: Pull all PRIORITY-tier leads first. Fill remaining slots up to [X] with the highest ICP-match-% leads from QUALIFIED tier. Exclude anything not disposition ACTIVE, and exclude leads without a usable LinkedIn profile URL.
Personalization: Use name, title, and company as baseline merge fields ({{firstName}}, {{jobTitle}}, {{companyName}}) for every lead. For leads where Traxy's signal data includes a specific, real reference (e.g. a named post, author, or topic they engaged with — not a generic "active ICP engager" summary), also write a one-line custom field (signalLine) referencing that specific engagement, and weave it into the message. For leads with only generic signal data, skip the signal line and rely on the name/title/company personalization — don't fabricate specificity that isn't there. Flag which leads got which treatment.
Build in HeyReach: Add the leads (with their custom fields) to a list or directly to a campaign via add_leads_to_list_v2 / add_leads_to_campaign_v2 (max 100 per call, so this fits in one batch). Draft one message template with the merge tags embedded in natural sentences, not bolted-on greetings. Check the campaign's existing sequence first (get_campaign_sequence) before writing a new one, so the personalized message step fits into whatever connection-request/follow-up structure already exists — build a new one only if none exists. Assign a LinkedIn sender account to the campaign. Preview the merged output on a handful of real leads to catch blank fields or broken sentences before anything goes live. Confirm daily send/invite volume stays within safe LinkedIn limits.
Before launching: Show me the selected lead list and the drafted message(s) for approval — don't start the campaign automatically.
```
## Next steps
With both connections in place, traxy pushes qualified leads into your HeyReach campaign automatically (or on your review), and Claude can query and act on that HeyReach data directly — checking campaign status, adding leads, or reporting on outreach performance.
# Connect ChatGPT/Codex to traxy
Source: https://docs.traxy.ai/using-traxy/connect-codex
traxy connects to Codex through a custom Streamable HTTP MCP server. No API key is required — the connection uses secure browser OAuth.
### 1 minute guide on how to connect traxy x ChatGPT/Codex!
In the traxy sidebar, go to [Integrations](https://app.traxy.ai/integrations), find the [Codex](https://app.traxy.ai/integrations/codex) card, and click **Configure**.
On the integration page, make sure the **App & browser** tab is selected (use the **Terminal** tab instead if you're connecting from the Codex CLI).
Click **Copy MCP URL** to copy the connector URL:
```text theme={null}
https://api.traxy.ai/api/v1/mcp
```
In the Codex app, open **Settings**, then under **Integrations** select **Plugins**.
On the **Plugins** page, switch to the **MCPs** tab, then click **Add** → **Add MCP server**.
In the **Connect to a custom MCP** form:
1. Enter `traxy.ai` as the **Name**.
2. Set **Type** to **Streamable HTTP**.
3. Paste the MCP URL — `https://api.traxy.ai/api/v1/mcp` — into the **URL** field.
4. Leave **Bearer token env var** and **Headers** blank.
5. Click **Save**.
Back on the **MCPs** tab, `traxy-ai` now appears in your **Servers** list with an **Authenticate** button. Click it.
You'll be redirected to traxy's authorization page:
* Select the **Workspace** you want Codex to access.
* Review the **Requested access** scopes (leads, analytics, ICP & Signal Brief, watchlist, integrations, agent tools, and more).
* Click **Approve**.
You'll be taken back to Codex settings, where `traxy-ai` now appears in the **Servers** list, toggled on with no pending authentication step — the connection is complete.
## Next steps
Once connected, you can ask Codex things like *"What's my traxy lead pipeline look like this week?"* or *"Pull my top-performing posts from traxy"* — Codex will call the relevant traxy tools directly.
To disconnect at any time, go to **Settings → Plugins → MCPs**, find `traxy-ai`, and toggle it off or remove it via the gear icon.
# Post Signals
Source: https://docs.traxy.ai/using-traxy/content-calendar
Find leads from LinkedIn posts and review post-level performance.
Use Post Signals to search monitored LinkedIn posts, start qualification, and review the leads tied to each post.
## Review the summary
The summary cards show:
* **Qualified Posts**
* **Total Leads from Posts**
* **Avg ICP Match**
* **Top Performing Account**
Choose **Last 7 days**, **Last 30 days**, **Last 90 days**, or **All time** before comparing results.
## Search and filter posts
You can:
* search post text
* switch between **List** and **Grid**
* sort by date, processing activity, qualification activity, lead count, average ICP match, or engagement
* filter by qualification status
* filter by **Auto-Scan**
* set a minimum average ICP match
Remove filters or widen the time range if a post you expect is not in the current result.
## Find leads from one post
Click **Find Leads** on a post with engagement.
The dialog can show a provisional range while traxy prepares an exact quote. When you continue, traxy obtains a ready quote and reserves the required credits before the request begins.
If the exact quote exceeds the workspace balance, the request does not start. traxy does not create unpaid usage.
People already charged for the same billable qualification window are deduplicated before settlement. The final credit use can therefore be lower than the raw engagement count.
## Find leads from a LinkedIn URL
Use the post URL action when a post is not already in your feed:
1. Click **Qualify Post**.
2. Paste the LinkedIn post URL.
3. Review the resolved post.
4. Review the exact credit requirement.
5. Click **Find Leads**.
traxy starts only after the post resolves and the credit reservation succeeds.
## Find leads from several posts
In list view, select the posts and open the batch action.
Every selected post needs a ready exact quote. traxy reserves the entire batch together. If the full reservation cannot succeed, none of the selected requests start.
## Understand Auto-Scan
For an active Watchlist profile, traxy automatically manages a sliding window of the five most recent posts published after you added the profile.
This trailing-five window is required. You cannot disable or shrink it. When a newer post enters the window, the oldest post leaves it.
Posts outside the managed window can still use manual **Find Leads**. An editable **Auto-Scan** setting on another post does not replace or expand the required Watchlist window.
## Understand the free initial discovery
The first time you add a Watchlist profile, traxy starts one free initial discovery:
* it freezes up to five recent posts available at add time
* it stops after finding five new qualified leads or examining the full frozen window
* pausing or removing the profile suspends that same discovery
* restoring the profile resumes it
* adding the same profile again does not create another free discovery
While that discovery is running, manual **Find Leads** and enabling an editable **Auto-Scan** setting for the profile are unavailable. Post Signals shows the current preparation or discovery status.
## Review post analytics
Open a post to see its performance and qualified leads. Follow a lead into **Leads** when you are ready to review, enrich, classify, or route the person.
# Dashboard
Source: https://docs.traxy.ai/using-traxy/dashboard
Review lead volume, audience patterns, and recent performance in traxy.
Use Dashboard for a current summary of your workspace.
## Review lead volume
The top cards show:
* **Total leads**, including the number added in the last 30 days
* **Avg leads per day**
* **Minimum ICP match**
The minimum ICP match controls which people qualify for your workspace. Raise it for stricter matching. Lower it to include more borderline matches.
Owners and admins can change the threshold. The control applies the new value when you commit the change.
## Read the leads-per-day chart
Use the chart to compare lead discovery and credit use over time.
Choose **7 Days**, **1 Month**, **3 Month**, or **All time**. The chart can separate:
* Agent leads
* Watchlist leads
* other lead sources
* credits used
* average ICP match
Use the same time range when you compare changes after an ICP or threshold update.
## Review live leads
**Live leads** shows the newest qualified leads first. Open a person to review the lead detail, or click **View all** to continue in **Leads**.
## Understand your audience
The audience section groups qualified leads by:
* title
* company size
* location
* industry
Use the strongest segment to see which part of your ICP is producing the most lead activity. These charts are aggregate summaries, not a replacement for the lead list.
## Review top performance
The top-performing section compares recent results over the last seven days.
* **Watchlist** highlights profiles producing useful lead signal.
* **Posts** highlights posts producing qualified leads.
Open the related profile or post when you want the underlying details.
If lead volume is low, compare the Agent state, Watchlist activity, ICP, and minimum match before changing several settings at once.
# ICP Configuration
Source: https://docs.traxy.ai/using-traxy/icp-configuration
Manage the ICP criteria traxy uses to identify and score leads.
Use ICP Configuration when you want to improve lead quality, widen lead volume, or adapt traxy to a new market.
## What you can edit
traxy splits ICP criteria into two parts:
* **People Criteria** for the individual you want to reach
* **Company Criteria** for the company you want to target
## People criteria
Use People Criteria to define the kind of person who should count as a fit.
The current public fields are:
* **Job Titles**
* **Departments**
* **Seniority Level**
* **Locations**
## Company criteria
Use Company Criteria to define the kind of company that should count as a fit.
The current public fields are:
* **Company Size**
* **Industries**
* **Revenue**
* **Funding**
* **Keywords & Niches**
* **Company / Product Summary**
traxy can prefill **Company / Product Summary** from your company context. Review it, edit it if needed, and confirm it when you want clearer buyer-fit scoring during qualification and enrichment.
## Update your ICP safely
Make small changes and then watch the results in **Dashboard**, **Leads**, and **Post Signals**.
* narrow your ICP when you are getting too many weak fits
* broaden your ICP when engagement exists but qualified leads stay low
* change one field at a time when you want cleaner feedback on what improved
## When to revisit it
Revisit ICP Configuration when:
* your team changes who it wants to target
* your content is attracting attention from the wrong audience
* you move into a new segment or geography
* lead quality changes after a campaign or content shift
Your ICP and your workspace threshold work together. If lead quality is close but volume is low, review both your ICP and your current dashboard threshold before making a bigger change.
# Integrations
Source: https://docs.traxy.ai/using-traxy/integrations
Connect traxy to AI clients, APIs, CRMs, alerts, outbound tools, and audience workflows.
Use Integrations to retrieve workspace data, work with traxy through an AI client, or route qualified leads to another system.
Owners and admins manage connections and automatic delivery settings.
## Data and AI access
Create keys for direct REST access to traxy data.
Connect Claude web, desktop, or Claude Code with OAuth.
Connect ChatGPT, the Codex app, IDE extension, or CLI with OAuth.
Give Ordinal aggregate audience access with a dedicated key.
## Lead delivery and audiences
Send qualified lead alerts to a Slack channel.
Send qualified leads to a campaign or lead list.
Send signed qualified lead events to your endpoint.
Start a Zap from qualified lead events.
Send qualified lead events to a Clay webhook.
Start an n8n workflow from qualified lead events.
Export qualified leads as a value-based audience CSV.
## Choose manual or automatic delivery
Slack, Webhook, Zapier, Clay, n8n, and HeyReach support manual delivery from **Leads**.
They can also route new qualified leads automatically when the lead meets the configured threshold. Automatic delivery starts with leads that qualify after you enable it. It does not backfill older leads.
Slack, Webhook, Zapier, Clay, and n8n can send repeat-engagement events. Repeat delivery requires the integration trigger and automatic delivery to remain enabled.
Use a test send before you rely on a destination. A webhook-style test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery can pause after repeated failures.
## Choose the right data connection
* Use **API** for application code that reads REST endpoints.
* Use **Claude** for Claude web, desktop, or Claude Code.
* Use **Codex** for ChatGPT and Codex surfaces.
* Use **Ordinal** for the dedicated aggregate audience workflow.
API keys are not required for Claude or Codex. Those connections use OAuth.
# API reference
Source: https://docs.traxy.ai/using-traxy/integrations/api-mcp/reference
Use the traxy REST API and understand the tools available through MCP.
Use REST for server-to-server reads. Use the traxy MCP connection when Claude or Codex should work with workspace data and confirmed actions.
Make a REST request and retrieve your first lead.
Authorize Claude with OAuth.
Authorize ChatGPT or Codex with OAuth.
## REST base URL
```text theme={null}
https://api.traxy.ai/api/v1
```
Send an API key as a bearer token:
```http theme={null}
Authorization: Bearer trxy_live_...
```
Do not send a workspace ID. traxy resolves the workspace from the credential.
## Get one lead
```sh theme={null}
curl --request GET \
--url "https://api.traxy.ai/api/v1/customer/leads?limit=1" \
--header "Authorization: Bearer trxy_live_..."
```
Lead list responses put records in `data` and pagination state in `page`.
## REST scopes
Default keys include these read scopes:
* `leads:read`
* `analytics:read`
* `icp:read`
* `watchlist:read`
* `content:read`
* `integrations:read`
* `sync:read`
* `agent:read`
* `workspace:read`
Optional permissions include:
* `leads:contact_read`
* `leads:contact_enrich`
* `leads:manage`
* `icp:manage`
* `watchlist:manage`
* `integrations:manage`
* `integrations:deliver`
* `agent:run`
* `audience_analytics:read`
* `audience_analytics:request`
* `post_qualification:manage`
The REST surface is read-first. Request-capable permissions protect the corresponding MCP tools. Contact enrichment also requires `leads:read` and `leads:contact_read`. Lead delivery also requires `leads:contact_read`.
## Pagination
Cursor-based lists default to 50 items and accept at most 100.
1. Send the first request without `cursor`.
2. Read `page.nextCursor`.
3. Pass that value unchanged in the next request.
4. Keep every filter and sort setting the same.
5. Stop when `page.nextCursor` is `null`.
Do not decode or construct cursors. A malformed or sort-incompatible cursor returns `400 validation_failed`.
`traxy_list_agent_candidates` is the exception. It uses `limit` and `offset`.
## Lead results
`GET /customer/leads` returns active leads by default. Use `disposition` when you want another lead view.
Lead, lead signal, and account report endpoints return leads with an ICP match of at least 50% by default. Pass `minIcpMatchPercent` to change that minimum. For example, `minIcpMatchPercent=0` also returns qualified engagers with a lower ICP match. Use `maxIcpMatchPercent` to set an upper bound.
Useful filters include:
* ICP match range
* lead tier
* lead state
* Agent or Watchlist origin
* monitored profile
* LinkedIn post
* engagement type, including post author
* owner
* company
* text query
* date range
Use `GET /customer/leads/signals` when you need the engagement, monitored profile, and post context behind the lead.
Use `GET /customer/analytics/meetings` for Meetings booked counts and `GET /customer/meetings` for the attributed meetings list. The meetings list accepts `range`, `leadId`, and `targetType`. Meeting attendee details require `leads:contact_read`.
Contact fields and LinkedIn profile URLs require `leads:contact_read`.
## MCP connection
The MCP endpoint is:
```text theme={null}
https://api.traxy.ai/api/v1/mcp
```
Claude and Codex complete OAuth in the browser. The client negotiates the protocol version. traxy supports `2025-11-25` and `2025-06-18`.
Any active workspace member can connect MCP. The approval screen shows the permissions available to your role in each workspace, and you choose what to grant. ICP and Watchlist changes require an owner or admin. Every tool call also checks your current role, so a role change takes effect on the next request.
One connection can include up to 50 workspaces that you select during approval. `traxy_list_workspaces` returns the workspaces available to the connection. Other tools accept an optional `workspaceId`. When you omit it, traxy uses the default workspace from the approval.
`tools/list` returns only the tools allowed by the approved scopes and current workspace access.
## MCP tools
The current catalog has 48 scope-gated tools.
### Connection and workspace
* `traxy_list_workspaces`
* `traxy_get_mcp_connection_status`
* `traxy_get_workspace_access`
### Leads and accounts
* `traxy_list_leads`
* `traxy_get_lead_counts`
* `traxy_get_lead_stats`
* `traxy_get_lead`
* `traxy_enrich_lead_contact`
* `traxy_list_lead_engagements`
* `traxy_list_lead_signals`
* `traxy_apply_lead_action`
* `traxy_list_account_reports`
* `traxy_get_account_report`
`traxy_apply_lead_action` supports `snooze`, `done`, `good`, `bad`, and `client`. The `done` action requires the user to confirm and the call to include `confirmDone: true`.
### Agent
* `traxy_get_agent_status`
* `traxy_get_agent_budget_status`
* `traxy_start_agent_run`
* `traxy_list_agent_runs`
* `traxy_list_agent_candidates`
Starting a run requires `confirmCreditSpend: true`. The client should ask before it makes the call.
### ICP and Watchlist
* `traxy_get_active_icp`
* `traxy_update_active_icp`
* `traxy_get_active_signal_brief`
* `traxy_update_active_signal_brief`
* `traxy_list_watchlist_profiles`
* `traxy_get_watchlist_profile`
* `traxy_get_watchlist_summary`
* `traxy_list_watchlist_recommendations`
* `traxy_add_watchlist_profile`
* `traxy_update_watchlist_profile`
* `traxy_remove_watchlist_profile`
* `traxy_restore_watchlist_profile`
ICP and Signal Brief updates require `icp:read` and `icp:manage`. Arrays you send replace the current values, and fields you omit stay unchanged.
Watchlist management supports teammate, competitor, influencer, investor, and custom relationships. A custom relationship requires its label.
### Content and analytics
* `traxy_get_analytics_dashboard`
* `traxy_get_meetings_summary`
* `traxy_list_meetings`
* `traxy_list_analytics_posts`
* `traxy_get_post_summary`
* `traxy_list_post_qualified_leads`
* `traxy_list_content_feed`
### Integrations and sync
* `traxy_get_integrations_status`
* `traxy_get_lead_delivery_state`
* `traxy_create_webhook_destination`
* `traxy_set_webhook_destination_enabled`
* `traxy_deliver_lead_to_webhook_destination`
* `traxy_get_sync_status`
* `traxy_get_latest_qualification_run`
Webhook-style destination tools support Webhook, Clay, n8n, and Zapier. Delivery requires the user to select the lead and destination.
### Audience and post qualification
* `traxy_get_audience_post`
* `traxy_find_audience`
* `traxy_qualify_linkedin_post`
* `traxy_get_organization_audience`
Audience reads return aggregate analytics. Audience discovery and post qualification can start work that uses credits. Post qualification requires `confirmCreditSpend: true`.
## MCP result filters
List tools use the same business filters as their REST counterparts where applicable.
* Lead tools accept ICP range, state, origin, monitored profile, post, engagement, owner, company, query, and date filters.
* Watchlist tools accept relationship, source, state, query, and sorting.
* Post tools accept monitored profile, relationship, source, date, ICP, qualification status, query, and sorting.
* Account reports accept company, ICP range, date, query, and aggregate sorting.
Use the tool schema returned by `tools/list` as the exact contract for the active grant.
## Errors
REST errors use this envelope:
```json theme={null}
{
"error": {
"code": "invalid_api_key",
"message": "Invalid API key.",
"status": 401,
"request_id": "req_..."
}
}
```
Common status codes:
* `400` for invalid input
* `401` for invalid, expired, or revoked credentials
* `402` for insufficient credits or access
* `403` when a browser origin is not allowed to call MCP
* `404` when the requested resource is not available to the workspace
* `409` for a malformed or unsupported LinkedIn post reference
* `429` for rate limits
* `503` when Meetings data is temporarily unavailable. Retry after the `Retry-After` delay.
Valid JSON-RPC requests use JSON-RPC errors for unknown methods, unknown tools, malformed calls, or missing scopes.
A known tool with invalid arguments returns `isError: true`. Read `structuredContent.error.issues`, fix the named argument paths, and retry.
## Data safety
* Store API keys and OAuth tokens as secrets.
* Do not send credentials in query parameters.
* Grant contact access only when the workflow needs it.
* Ask before any tool spends credits or changes workspace data.
* Revoke keys and disconnect clients that are no longer used.
# Clay
Source: https://docs.traxy.ai/using-traxy/integrations/clay
Send qualified lead events from traxy to a Clay webhook.
Use the Clay integration when you want qualified lead events from traxy to flow into a Clay workflow or table.
Clay delivery uses a webhook-style connection. traxy sends a signed `POST` request to the Clay webhook URL you configure.
## Before you connect Clay
Owners and admins can connect Clay and change delivery settings.
Make sure you have:
* a Clay account
* a Clay table, workflow, or webhook destination ready to receive lead data
* the Clay webhook URL
* an optional bearer token if your Clay endpoint expects one
Use a secure `https://` URL. traxy cannot send to insecure endpoints.
## Connect Clay
1. Open **Integrations**.
2. Open **Clay**.
3. Add an **Integration Name**.
4. Paste the **Webhook URL** from Clay.
5. Add an **Auth Header** if your Clay endpoint expects one.
6. Click **Connect**.
7. Review the **Qualified Lead Detected** trigger.
8. Choose whether to keep auto-send on.
9. Set the ICP match threshold for automatic delivery.
10. Decide whether to enable **Send repeat engagement from qualified leads**.
11. Click **Save Configuration**.
12. Click **Send Test Payload** before you rely on the workflow.
If you connect Clay but do not keep a valid webhook URL saved, Clay delivery stays disabled.
## Choose manual or automatic delivery
Clay can work in two ways:
* **Manual delivery** from the leads table when you want to review each lead first
* **Automatic delivery** when you want traxy to send new qualified leads to Clay as soon as they meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on.
Repeat engagement delivery only works when the Clay trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.
## Send leads manually
Use manual delivery when you want to control which leads enter Clay.
1. Open **Leads**.
2. Select one or more leads.
3. Choose the send action.
4. Select **Clay**.
5. Confirm the send.
traxy queues the selected leads for delivery to the configured Clay webhook.
## Review the payload
The Clay integration page includes **Payload & Help** with sample JSON for first qualified lead delivery and repeat engagement delivery.
The payload includes event metadata plus lead, profile, company, contact, and engagement data.
Use the sample payload in traxy as the source of truth when you map fields in Clay.
## Verify requests
Clay requests are signed.
Each request includes `X-Traxy-Signature` and `X-Traxy-Timestamp` so your receiver can verify that it came from traxy.
If you add an auth header, use the bearer format shown in the app.
## Test and troubleshoot
Use **Send Test Payload** before you turn on an important workflow.
The test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery may pause if repeated failures are not fixed.
If you send manually from **Leads**, you may see states such as queued, delivered, or failed. Fix the underlying Clay issue first, then retry from the lead.
Review automatic settings carefully before you enable them for a shared workspace.
## Disconnect Clay
Use **Disconnect** when you want traxy to stop sending events to Clay.
Disconnecting Clay does not change existing Clay tables, workflows, or records.
# HeyReach
Source: https://docs.traxy.ai/using-traxy/integrations/heyreach
Send qualified leads from traxy to a HeyReach campaign or lead list.
Use the HeyReach integration when you want to move qualified leads from traxy into a HeyReach outbound workflow.
You can send leads to a campaign or to a lead list. Use a campaign when you want leads to enter an active outreach sequence. Use a lead list when you want to collect leads in HeyReach before you decide how to use them.
## Before you connect HeyReach
Owners and admins can connect HeyReach and change delivery settings.
Make sure you have:
* a HeyReach account
* a HeyReach API key
* a campaign or lead list you want to use, unless you plan to create one from traxy
* at least one active HeyReach sender account if you plan to create a campaign from traxy
traxy sends leads to HeyReach by LinkedIn profile URL. If a lead is missing a LinkedIn profile URL, HeyReach delivery cannot complete for that lead.
## Connect HeyReach
1. Open **Integrations**.
2. Open **HeyReach**.
3. Paste your **HeyReach API key**.
4. Click **Connect**.
5. Choose a **Destination type**.
6. Select **Campaign** or **Lead list**.
7. Choose an existing destination, or create a new one from traxy.
8. Choose **Manual** or **Auto** delivery.
9. Click **Save settings**.
If you connect HeyReach but do not select a destination, HeyReach delivery stays disabled.
## Choose a destination
Use **Campaign** when you want qualified leads to go directly into a HeyReach campaign.
When you select a campaign, traxy sends leads to that campaign and adds traxy tracking fields and tags for reporting.
Use **Lead list** when you want traxy to add qualified leads to a list first.
Lead lists are useful when you want to review, segment, or attach leads to campaigns inside HeyReach later.
## Create a lead list from traxy
1. In the HeyReach integration, set **Destination type** to **Lead list**.
2. Click **Create new lead list**.
3. Add a list name.
4. Click **Create list**.
5. Save the HeyReach settings.
traxy creates an empty HeyReach lead list and selects it as the destination.
## Create a campaign from traxy
1. In the HeyReach integration, set **Destination type** to **Campaign**.
2. Click **Create new campaign**.
3. Add a campaign name.
4. Select a lead list, or create a new lead list.
5. Select one or more sender accounts.
6. Click **Create campaign**.
7. Click **Finish setup in HeyReach**.
8. Finish the sequence setup in HeyReach.
9. Return to traxy and click **Done**.
10. Save the HeyReach settings.
Campaigns created from traxy start as drafts. Finish the campaign sequence in HeyReach before you turn on **Auto** delivery.
## Choose manual or automatic delivery
HeyReach can work in two ways:
* **Manual delivery** from the leads table when you want to review each lead first
* **Automatic delivery** when you want traxy to send new qualified leads to HeyReach as soon as they meet the workspace ICP threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on.
Auto-send requires a saved HeyReach destination. If the selected campaign is still a draft, finish the campaign setup in HeyReach before you enable **Auto**.
## Send leads manually
Use manual delivery when you want more control over who enters HeyReach.
1. Open **Leads**.
2. Select one or more leads.
3. Choose the send action.
4. Select **HeyReach**.
5. Confirm the send.
traxy queues the selected leads for delivery to the configured HeyReach destination.
## Track performance
After HeyReach is connected, the integration page shows performance for the selected destination.
For campaign destinations, you can review:
* total campaign leads
* acceptance rate
* reply rate
* traxy-sent leads
* accepted connections
* replies
* interested replies when HeyReach sync data is available
For lead list destinations, traxy shows list totals and delivery counts. Campaign acceptance and reply stats appear after you send to a campaign destination.
## What traxy sends
traxy sends the lead's LinkedIn profile URL, name, company, role, location, summary, and email when available.
traxy also adds tracking fields such as lead ID, lead URL, ICP score, lead tier, intent level, source, and sent time. HeyReach leads can also receive traxy tags so you can find them later in HeyReach.
## Disconnect HeyReach
Use **Disconnect** when you want traxy to stop sending leads to HeyReach.
Disconnecting HeyReach does not change existing HeyReach leads, lead lists, or campaigns.
# Meta Ads
Source: https://docs.traxy.ai/using-traxy/integrations/meta-ads
Export high-ICP-match leads from traxy as a value-based audience CSV for Meta Ads.
Use the Meta Ads integration when you want to turn qualified traxy leads into a value-based audience CSV for Meta.
traxy includes leads at or above the ICP match threshold shown in the app. The row value is the ICP match, so stronger-fit leads carry more value in the export.
## Before you start
Make sure you have:
* access to the right Meta business account and ad account
* permission to create audiences in Meta Ads
* the Meta Ads integration available in **Integrations**
* qualified leads in traxy
* permission to use the exported contacts for advertising
Customer lists contain personal identifiers. Only export and upload contacts you have permission to use for advertising, and follow Meta's customer list terms.
## Start an export in traxy
1. Open **Integrations**.
2. Open **Meta Ads**.
3. Review **Audience size**.
4. Click **New export**.
5. Review the **Audience snapshot**.
6. Choose the export accuracy.
7. Review the credit estimate if traxy shows one.
8. Click **Start export**.
Running exports appear in **Export history** while traxy prepares the CSV.
## Choose export accuracy
Choose the accuracy option that fits your goal:
* **Maximum match data** enriches email and phone before generating the audience.
* **Medium, email only** enriches missing emails and keeps phone fields as-is.
* **Medium, phone only** enriches missing phone numbers and keeps email fields as-is.
* **Fastest, no enrichment** uses the contact data already saved on each lead.
More contact fields can help Meta match more people, but enrichment may use credits. Trial exports use the trial behavior shown in the app.
## Download the CSV
Export history can show:
* **Queued**
* **Processing**
* **Ready**
* **Failed**
When an export is **Ready**, click the download action to save the CSV.
Upload the exact file traxy gives you. Do not rename columns, split email and phone into separate files, or reformat phone numbers unless your team has a required cleanup step.
## Upload the list in Meta Ads
1. Go to your Meta business account.
2. Open **Audiences**.
3. Click **Create audience**.
4. Choose **Custom audience**.
5. Choose **Customer list**.
6. Upload the file you exported from traxy.
7. Accept Meta's customer list terms if Meta prompts you.
8. Map the traxy columns to Meta identifiers.
9. Use **Email** for email addresses and **Phone** for phone numbers.
10. Name the audience clearly, such as `traxy - qualified leads - current`.
11. Finish the import and wait for Meta to process the audience.
Meta may take time to match the uploaded identifiers. Wait until the audience is ready before you use it in an ad set or as a lookalike source.
## Create a lookalike audience
1. In **Audiences**, click **Create audience**.
2. Choose **Lookalike audience**.
3. Select the traxy customer list Custom Audience as the source.
4. Choose the countries or regions you want to reach.
5. Start with a close lookalike size when available.
6. Create broader lookalike variants separately when you want to test scale.
7. Name the audience clearly, such as `traxy - qualified leads - 1% lookalike - US`.
8. Create the audience and wait for Meta to finish building it.
If Meta cannot create the lookalike, the source audience may be too small or still processing. Export a larger qualified list, broaden your traxy ICP, or wait for the customer list audience to finish matching.
## Refresh the audience
Refresh the Meta customer list when your qualified lead pool changes meaningfully.
You can update the same customer list when you want Meta campaigns and related lookalikes to keep using the latest source. Create a new dated audience when you want to compare one export against another.
If match quality looks weak, check whether the export includes enough email and phone data, whether phone numbers include country context, and whether you uploaded the unedited traxy file.
# n8n
Source: https://docs.traxy.ai/using-traxy/integrations/n8n
Send qualified lead events from traxy to an n8n webhook.
Use the n8n integration when you want qualified lead events from traxy to start an n8n workflow.
n8n delivery uses a webhook-style connection. traxy sends a signed `POST` request to the n8n webhook URL you configure.
## Before you connect n8n
Owners and admins can connect n8n and change delivery settings.
Make sure you have:
* an n8n workspace or instance
* an n8n workflow with a webhook trigger ready to receive data
* the n8n webhook URL
* an optional bearer token if your webhook expects one
Use a secure `https://` URL. traxy cannot send to insecure endpoints.
## Connect n8n
1. Open **Integrations**.
2. Open **n8n**.
3. Add an **Integration Name**.
4. Paste the **Webhook URL** from n8n.
5. Add an **Auth Header** if your n8n webhook expects one.
6. Click **Connect**.
7. Review the **Qualified Lead Detected** trigger.
8. Choose whether to keep auto-send on.
9. Set the ICP match threshold for automatic delivery.
10. Decide whether to enable **Send repeat engagement from qualified leads**.
11. Click **Save Configuration**.
12. Click **Send Test Payload** before you rely on the workflow.
If you connect n8n but do not keep a valid webhook URL saved, n8n delivery stays disabled.
## Choose manual or automatic delivery
n8n can work in two ways:
* **Manual delivery** from the leads table when you want to review each lead first
* **Automatic delivery** when you want traxy to send new qualified leads to n8n as soon as they meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on.
Repeat engagement delivery only works when the n8n trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.
## Send leads manually
Use manual delivery when you want to control which leads enter n8n.
1. Open **Leads**.
2. Select one or more leads.
3. Choose the send action.
4. Select **n8n**.
5. Confirm the send.
traxy queues the selected leads for delivery to the configured n8n webhook.
## Review the payload
The n8n integration page includes **Payload & Help** with sample JSON for first qualified lead delivery and repeat engagement delivery.
The payload includes event metadata plus lead, profile, company, contact, and engagement data.
Use the sample payload in traxy as the source of truth when you map fields in n8n.
## Verify requests
n8n requests are signed.
Each request includes `X-Traxy-Signature` and `X-Traxy-Timestamp` so your receiver can verify that it came from traxy.
If you add an auth header, use the bearer format shown in the app.
## Test and troubleshoot
Use **Send Test Payload** before you turn on an important workflow.
The test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery may pause if repeated failures are not fixed.
If you send manually from **Leads**, you may see states such as queued, delivered, or failed. Fix the underlying n8n issue first, then retry from the lead.
Review automatic settings carefully before you enable them for a shared workspace.
## Disconnect n8n
Use **Disconnect** when you want traxy to stop sending events to n8n.
Disconnecting n8n does not change existing n8n workflows or execution history.
# Ordinal
Source: https://docs.traxy.ai/using-traxy/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
Owners and admins can generate an Ordinal key in traxy.
Make sure you have:
* access to the traxy workspace you want to connect
* a paid 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 **Integrations**.
2. Open **Ordinal**.
3. Generate the Ordinal API key.
4. Copy the key when traxy shows it.
5. 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.
`GET /audience-analytics/health`
`GET /audience-analytics/linkedin-posts`
`POST /audience-analytics/linkedin-posts/find-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 credits. If discovery is not available, review your workspace access and credits 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/using-traxy/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/using-traxy/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/using-traxy/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.
# Get workspace audience
Source: https://docs.traxy.ai/using-traxy/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.
# API
Source: https://docs.traxy.ai/using-traxy/integrations/rest-api
Create an API key and retrieve traxy workspace data with a simple REST request.
Use the API when your application needs direct, server-to-server access to traxy data.
The fastest path is to create a key and request one lead. You do not need to send a workspace ID. The API identifies your workspace from the key.
API access requires Pro, Scale, or Enterprise access.
## Get your first lead
Open **Integrations** > **API**, then click **Create key**.
Give the key a clear name. The default read scopes are enough to retrieve leads. Add contact access only if your application needs saved email, phone, or LinkedIn profile data.
Copy the full key from the confirmation dialog and store it in a secret manager.
traxy shows the full key once. If you lose it, revoke it and create another key.
Replace the example key, then run:
```sh theme={null}
curl --request GET \
--url "https://api.traxy.ai/api/v1/customer/leads?limit=1" \
--header "Authorization: Bearer trxy_live_..."
```
The lead is in `data[0]`. If `data` is empty, your workspace does not currently have an active lead that matches the request.
By default, the API returns leads with an ICP match of at least 50%. Add `minIcpMatchPercent=0` to include qualified engagers with a lower ICP match.
Browse every REST endpoint, parameter, scope, and response schema.
## Create and revoke keys
Owners and admins can create and revoke API keys. Members can view setup guidance but cannot manage keys.
To create a key:
1. Open **Integrations**.
2. Open **API**.
3. Click **Create key**.
4. Enter a name.
5. Select the scopes your application needs.
6. Click **Create key**.
7. Copy and store the key.
To revoke a key:
1. Open **Integrations** > **API**.
2. Find the key.
3. Click **Revoke**.
4. Confirm the change.
Revocation stops new requests that use that key.
## Choose scopes
New API keys start with read access for leads, analytics, ICP, Watchlist, content, integrations, sync status, Agent status, and workspace access.
Add only the permissions your application needs:
* `leads:contact_read` returns saved contact fields and LinkedIn profile URLs.
* `leads:contact_enrich` allows contact enrichment and requires lead read and contact read access.
* `leads:manage` allows lead quick actions.
* `icp:manage` allows updates to the active ICP and Signal Brief.
* `watchlist:manage` allows Watchlist changes.
* `integrations:manage` allows webhook destination changes.
* `integrations:deliver` allows delivery of a selected lead to a webhook-style destination.
* `agent:run` allows a confirmed Agent run.
* `audience_analytics:read` returns aggregate audience analytics.
* `audience_analytics:request` starts audience discovery.
* `post_qualification:manage` starts confirmed qualification for a LinkedIn post.
Some permissions can spend credits or change workspace data. The app calls them out during key creation. Only owners and admins can grant sensitive access.
API keys are for REST requests. Claude and Codex connect through OAuth and do not need an API key.
## Paginate results
List endpoints return `page.nextCursor`.
1. Send the first request without `cursor`.
2. Copy `page.nextCursor` into the next request.
3. Keep the same filters and sorting.
4. Stop when `page.nextCursor` is `null`.
Treat the cursor as an opaque value. Do not edit or decode it.
## Keep keys safe
* Store keys in a secret manager.
* Do not put keys in browser code, source control, documentation, or chat.
* Use separate keys for separate applications.
* Review each key's **Last used** date.
* Revoke a key when an application no longer needs access.
If you want to ask for leads in natural language, connect [Claude](/using-traxy/integrations/claude) or [Codex](/using-traxy/integrations/codex).
# Slack
Source: https://docs.traxy.ai/using-traxy/integrations/slack
Send qualified lead alerts and workspace activity notifications from traxy to Slack.
Use the Slack integration when you want qualified lead alerts and workspace activity notifications inside a Slack channel.
## Before you connect Slack
Owners and admins can connect Slack and change delivery settings.
Decide which channel should receive traxy notifications before you start. If you want to use a private channel and it does not appear in the channel list, invite traxy into that channel with `/invite @traxy`.
## Connect Slack
1. Open **Integrations**.
2. Open **Slack**.
3. Connect your Slack workspace.
4. Select the channel that should receive notifications, or create a public or private channel from traxy.
5. Enable the **Qualified Lead Detected** trigger once the channel is set.
6. Choose which Watchlist profiles should send notifications, or leave the selector empty for all Watchlist profiles.
7. Decide whether you want auto-send on or off.
8. If you turn on auto-send, set the ICP match threshold that should trigger delivery.
9. Decide whether to enable **Send repeat engagement from qualified leads**.
10. Decide whether to enable **Send Daily Summary**.
11. Send a test event before you rely on it.
If you connect Slack but do not select a channel, Slack stays disabled.
## Choose manual or automatic delivery
Slack can work in two ways:
* **Manual delivery** from the leads table when you want to review each lead first
* **Automatic delivery** when you want traxy to send qualified lead alerts as soon as leads meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on.
Repeat engagement delivery only works when the integration trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.
## Filter by Watchlist profile
Use **Watchlist Profiles** when you want Slack alerts only from specific monitored profiles.
Leave the selector empty to receive alerts from all Watchlist profiles. Select one or more profiles when a channel should only receive leads from those sources.
## Send a daily summary
Turn on **Send Daily Summary** when you want a daily recap of all qualified leads found by traxy.
The summary sends to the selected Slack channel every day at the time shown in the app. If no channel is selected, the daily summary control stays disabled.
## Test and troubleshoot
Use a test send before you go live.
Send a test before you rely on the channel. Automatic delivery retries temporary failures and may pause if repeated failures are not fixed.
If you send manually from **Leads**, you may see states such as queued, delivered, or failed. Fix the underlying Slack issue first, then retry from the lead.
Review automatic settings carefully before you enable them for a shared workspace.
# Webhook
Source: https://docs.traxy.ai/using-traxy/integrations/webhook
Send qualified lead events from traxy to another system with a signed Webhook request.
Use the Webhook integration when you want traxy to send qualified lead events to another system.
Webhook delivery is designed for qualified lead workflows. Keep the receiver focused on lead routing and downstream automation.
## Before you connect Webhook
Owners and admins can create or change the Webhook integration.
Make sure you have a secure `https://` endpoint ready before you start. If your receiver expects authentication, prepare the auth header value your team wants to use.
Each workspace supports one active Webhook integration. If you need to change destinations, update the existing Webhook instead of creating parallel ones.
## Connect Webhook
1. Open **Integrations**.
2. Open **Webhook**.
3. Add an integration name.
4. Add a secure `https://` endpoint.
5. Add an auth header if your receiver expects one.
6. Enable the **Qualified Lead Detected** trigger.
7. Decide whether you want auto-send on or off.
8. If you turn on auto-send, set the ICP match threshold that should trigger delivery.
9. Decide whether to enable **Send repeat engagement from qualified leads**.
10. Open **Payload & Help** if you want to review the sample payload and signing guidance.
11. Send a test payload before you rely on it.
## Review the payload
The Webhook UI includes a payload browser and sample JSON.
The payload includes event metadata plus lead, profile, company, contact, and engagement data.
Use the payload samples in the app as the source of truth for your receiver. They cover first qualified lead delivery and repeat engagement delivery.
## Verify requests
Webhook requests are signed.
Each request includes `X-Traxy-Signature` and `X-Traxy-Timestamp` so your receiver can verify that it came from traxy.
## Choose manual or automatic delivery
Webhook can work in two ways:
* **Manual delivery** from the leads table when you want to review each lead first
* **Automatic delivery** when you want traxy to send qualified lead events as soon as leads meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on.
Repeat engagement delivery only works when the integration trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.
## Test and troubleshoot
Use a test payload before you go live.
The test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery may pause if repeated failures are not fixed.
If you send manually from **Leads**, you may see states such as queued, delivered, or failed. Fix the underlying Webhook issue first, then retry from the lead.
Review automatic settings carefully before you enable them for a shared workspace.
# Zapier
Source: https://docs.traxy.ai/using-traxy/integrations/zapier
Send qualified lead events from traxy to a Zapier webhook.
Use the Zapier integration when you want qualified lead events from traxy to start a Zapier automation.
Zapier delivery uses a webhook-style connection. traxy sends a signed `POST` request to the Zapier webhook URL you configure.
## Before you connect Zapier
Owners and admins can connect Zapier and change delivery settings.
Make sure you have:
* a Zapier account
* a Zap with a webhook trigger ready to receive data
* the Zapier webhook URL
* an optional bearer token if your receiving step expects one
Use a secure `https://` URL. traxy cannot send to insecure endpoints.
## Connect Zapier
1. Open **Integrations**.
2. Open **Zapier**.
3. Add an **Integration Name**.
4. Paste the **Webhook URL** from Zapier.
5. Add an **Auth Header** if your Zap expects one.
6. Click **Connect**.
7. Review the **Qualified Lead Detected** trigger.
8. Choose whether to keep auto-send on.
9. Set the ICP match threshold for automatic delivery.
10. Decide whether to enable **Send repeat engagement from qualified leads**.
11. Click **Save Configuration**.
12. Click **Send Test Payload** before you rely on the Zap.
If you connect Zapier but do not keep a valid webhook URL saved, Zapier delivery stays disabled.
## Choose manual or automatic delivery
Zapier can work in two ways:
* **Manual delivery** from the leads table when you want to review each lead first
* **Automatic delivery** when you want traxy to send new qualified leads to Zapier as soon as they meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on.
Repeat engagement delivery only works when the Zapier trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.
## Send leads manually
Use manual delivery when you want to control which leads enter a Zap.
1. Open **Leads**.
2. Select one or more leads.
3. Choose the send action.
4. Select **Zapier**.
5. Confirm the send.
traxy queues the selected leads for delivery to the configured Zapier webhook.
## Review the payload
The Zapier integration page includes **Payload & Help** with sample JSON for first qualified lead delivery and repeat engagement delivery.
The payload includes event metadata plus lead, profile, company, contact, and engagement data.
Use the sample payload in traxy as the source of truth when you map fields in Zapier.
## Verify requests
Zapier requests are signed.
Each request includes `X-Traxy-Signature` and `X-Traxy-Timestamp` so your receiver can verify that it came from traxy.
If you add an auth header, use the bearer format shown in the app.
## Test and troubleshoot
Use **Send Test Payload** before you turn on an important automation.
The test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery may pause if repeated failures are not fixed.
If you send manually from **Leads**, you may see states such as queued, delivered, or failed. Fix the underlying Zapier issue first, then retry from the lead.
Review automatic settings carefully before you enable them for a shared workspace.
## Disconnect Zapier
Use **Disconnect** when you want traxy to stop sending events to Zapier.
Disconnecting Zapier does not change existing Zaps or Zap history.
# Leads
Source: https://docs.traxy.ai/using-traxy/leads
Review, classify, enrich, export, and route qualified leads in traxy.
Use Leads to work with the people traxy qualified from Agent, Watchlist, and post activity.
## Use the lead views
traxy separates leads into five views:
* **Active Leads** for people ready for review or outreach
* **Clients** for people you identify as customers
* **Snooze** for people you want to revisit later
* **Done** for outreach or review work you completed
* **Bad fit** for people who should not count as a fit
**Done** does not change the lead's ICP match or fit feedback. It removes the person from active lead results in the app, API, and connected AI clients. Move the lead back to **Active Leads** when you want to resume work.
## Search and filter
Use search, ICP match, intent, relationship strength, owner, monitored profile, post source, and engagement filters to narrow the list.
**Advanced Filters** adds people, company, date, and delivery criteria. Use it when you need a repeatable segment for review, export, or routing.
If your workspace has more than one profile scope, choose the scope before you compare counts or export results.
## Review a lead
Open a lead to review:
* the qualification summary
* ICP match
* engagement history
* source profile and post
* fit feedback and notes
* saved contact data
* delivery status
Use **Edit Columns** to keep the table focused on the fields your workflow needs.
## Use quick actions
You can act from the table or lead detail:
* **Mark as client**
* **Snooze lead**
* **Mark as done**
* **Mark as good fit**
* **Mark as bad fit**
Good-fit and bad-fit actions accept preset reasons and a note. traxy uses this feedback to improve future qualification.
You can apply supported actions to selected leads in bulk. Marking a lead as done is reversible.
## Enrich contact data
Use enrichment when you need a saved email, phone number, or both.
Owners and admins can also configure **Auto-Enrich** for newly qualified leads at or above a selected ICP match. Auto-Enrich applies to future qualified leads, not older posts or leads.
Credits settle only when traxy finds and saves new contact data:
* email enrichment uses 3 credits
* phone enrichment uses 5 credits
If the contact data is already saved, read it from the lead instead of enriching it again.
## Export or send leads
Select leads to export the columns your workflow needs.
You can also send a lead to a configured Slack, Webhook, Zapier, Clay, n8n, or HeyReach destination. Automatic delivery applies to leads that qualify after you enable it. Send older leads manually.
## Exclude a company
Use the company hover card to add a company domain to **Blocklist**. Future leads from that domain no longer enter your workspace.
Manage exclusions in **Settings** > **Blocklist**.
When the workspace has no credits left, new credit-funded qualification and enrichment requests pause or fail until the monthly credit window resets or the plan changes. Existing saved leads remain available.
# Agency outbound playbook
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-agencies
Use signal-based outbound to sell services with more trust, relevance, and selectivity.
Use this playbook when you sell agency or consulting services and want your outreach to demonstrate judgment, not just availability.
## What is different for agencies
Agency buying is more relationship-driven than product-led. Prospects are often evaluating your thinking before they evaluate your offer.
That means the first touch should prove you understand the problem, not just announce that your agency exists.
## Signals that matter most
Prioritize in this order:
1. Engagement on a problem your agency solves
2. Public frustration with a current approach or result
3. Engagement with your case studies or thought leadership
4. Hiring activity that points to a capability gap your agency could support
5. Shared engagement paths that could create a warm introduction
## Best channel and timing
LinkedIn is often the best first channel for agencies because it feels more like a peer conversation.
Email works well when:
* the signal is strong
* you have a relevant case study
* you want to share a sharper observation with more context
Move within 48 hours for content engagement signals. Event or hiring-based signals can sometimes stay workable a bit longer, but freshness still helps.
## Messaging angle
Lead with a useful observation or short insight.
Good agency angles:
* a quick read on what is likely going wrong
* a relevant example from a similar company
* a concrete offer to share a teardown, resource, or short case study
## Suggested sequence
1. Day 0: LinkedIn note or email based on signal strength
2. Day 3: follow-up with a useful example, teardown, or case study
3. Day 7: one final note with a softer interest-based ask
## Example LinkedIn message
```text theme={null}
Hey [Name], your take on [topic] resonated.
We have been seeing the same pattern with [their company type] teams lately.
We just worked through this with a similar company. Happy to share what helped if useful.
```
## Example email
```text theme={null}
Subject: [topic]
[First name] - your post on [topic] caught my eye.
The issue you pointed to is usually where [their company type] teams start to lose momentum.
If useful, I can send over a short example of how another team tackled it.
```
## Common mistakes
* leading with credentials instead of the prospect’s problem
* asking for a call before demonstrating value
* treating every company with an obvious problem as a good fit
* describing your agency so vaguely that the buyer still does not know what you actually help with
## What good looks like
* the prospect feels understood before they feel sold
* your first touch gives value or framing, not just a request
* selectivity improves because you focus on clear problem signals, not generic awareness
For the broader framework, use [outbound to signal-based leads](/using-traxy/outbound-to-signal-based-leads).
# Content-led outbound playbook
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-content-led
Turn engagement on your own LinkedIn content into qualified conversations.
Use this playbook when your team posts on LinkedIn and wants to convert the right engagement into pipeline without sounding pushy.
## Why this motion works
This is the warmest form of signal-based outbound. The lead did not just match your ICP. They engaged with your ideas directly.
You are not inventing a reason to reach out. You are continuing a conversation they already started.
## Signals that matter most
Prioritize in this order:
1. Thoughtful comments that show real understanding of the topic
2. Repeat engagement across multiple posts
3. Shares or reposts of your content
4. Engagement from multiple people at the same target account
5. Light reactions from strong ICP matches
## Best channel and timing
LinkedIn is usually the best first channel because the conversation started there.
* Reply publicly within 24 hours if the person commented.
* Follow with a DM after the public reply if the fit is strong.
* Use email later if the signal stays warm and you want to share something more detailed.
## Messaging angle
Lead with the topic they engaged with, then bridge to one useful next step.
Good first angles:
* a practical resource
* a short example from another team
* a sharp question tied to the issue they raised
Do not jump straight to a meeting ask.
## Suggested sequence
1. Day 0: reply to the public comment
2. Day 0 or 1: send a short LinkedIn DM
3. Day 3 or 4: send a follow-up with a useful example or resource
4. Day 7: close the loop with one simple question
## Example DM
```text theme={null}
Hey [Name], really appreciated your take on [topic].
The point you made about [specific thing] is something we see a lot with [their company type] teams.
Happy to send over a short breakdown of what seems to work here if useful.
```
## Example email follow-up
```text theme={null}
Subject: [topic]
[First name] - following up on your comment about [topic].
You called out [specific issue], which is exactly where a lot of teams get stuck.
If helpful, I can send over the short version of what we see work most often.
```
## Common mistakes
* sending DMs to everyone who liked a post
* skipping the public reply and jumping straight to a pitch
* sending a private message that could have gone to anyone
* treating every engaged person as sales-ready
## What good looks like
* comments and repeat engagement outperform likes
* public replies make private follow-up feel natural
* the best conversations start from one clear topic, not a full product pitch
For the broader framework, use [outbound to signal-based leads](/using-traxy/outbound-to-signal-based-leads).
# Events outbound playbook
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-events
Work pre-event, during-event, and post-event signals before the event context fades.
Use this playbook when your team wants to convert event activity into better conversations.
## What is different about event signals
Event signals are time-bound. Their strength comes from shared context and urgency.
The biggest mistake is waiting until the event memory fades, then sending generic follow-up that could have gone to anyone.
## Signals that matter most
Prioritize in this order:
1. Pre-event engagement with agenda, speaker, or topic posts
2. Live engagement during a session or around an event theme
3. Post-event takeaways, recaps, or topic discussion
4. Multiple people from a target account engaging around the same event
5. Speaker or panel engagement tied closely to your offer
## Work the event in three phases
### Pre-event
Use this window to book meetings or start conversations before the event starts.
* watch who engages with speaker announcements, agenda posts, and event topics
* reach out to strong-fit leads with a lightweight note
* aim to set up a short meeting or a hallway conversation, not a full pitch
### During the event
This is the fastest-moving phase.
* monitor live posts, comments, and takeaways
* use LinkedIn for real-time, conversational follow-up
* keep the message short and tied to the exact session or topic
### Post-event
This is where most teams slow down too much.
* send the first follow-up within 24 to 48 hours
* reference the exact topic, session, or takeaway
* add one useful angle or resource instead of sending a generic “great meeting you” note
## Best channel and timing
* LinkedIn during the event and right after it
* Email when you want to send something more substantive after the event
If more than a week has passed, the event context is no longer doing much work for you.
## Suggested sequence
1. Pre-event: one lightweight setup note
2. During event: short LinkedIn touch tied to the live topic
3. Within 48 hours after: email with one specific takeaway or resource
4. Days 4 to 7 after: one follow-up with a new angle
## Example post-event email
```text theme={null}
Subject: [session topic] at [event]
Hey [Name],
Saw your takeaway on [session topic] at [event].
The point about [specific idea] is something we keep seeing with [their company type] teams as well.
If useful, I can send over a short breakdown of how teams are handling it.
```
## Common mistakes
* waiting too long after the event
* sending the same follow-up to everyone who attended
* referencing the event without any real substance
* building the post-event sequence only after the event is over
* ignoring strong pre-event signals that could have created meetings earlier
## What good looks like
* strong event signals are worked quickly
* the message references a real session, topic, or takeaway
* your best event follow-up feels like continuation, not re-introduction
For the broader framework, use [outbound to signal-based leads](/using-traxy/outbound-to-signal-based-leads).
# SaaS outbound playbook
Source: https://docs.traxy.ai/using-traxy/outbound-playbook-saas
Work signal-based leads in SaaS with better prioritization, messaging, and multi-threading.
Use this playbook when you sell software and want to turn engagement signals into stronger outbound.
## What is different in SaaS
SaaS outbound is crowded. Buyers get too much generic outreach, and buying decisions often involve multiple stakeholders.
That makes signal quality more valuable. When a lead engages with a problem your product solves, you can be specific without guessing.
## Signals that matter most
Prioritize in this order:
1. Comments on a problem your product solves
2. Multiple people from the same account engaging with related topics
3. Repeat engagement from a decision-maker
4. Engagement around competitor or comparison content
5. Fresh role changes for strong-fit leaders, especially when paired with topic engagement
## Best channel and timing
Use email first when the ICP fit and signal are both strong.
Use LinkedIn first when:
* the signal is lighter
* the engagement happened on LinkedIn
* you want a lower-friction opener before sending a fuller business case
Move within 24 to 48 hours while the topic is still current.
## Messaging angle
Lead with the problem they engaged with, not your product.
Good angles:
* a problem pattern you keep seeing in similar teams
* a short operational observation
* a practical takeaway that makes the issue easier to frame internally
## Multi-thread the right way
If multiple people from one company engage, do not send the same note to everyone.
* send the most senior contact a concise email tied to business impact
* send a lighter LinkedIn note to a more junior or hands-on contact
* keep the topic consistent, but adapt the angle to the role
## Suggested sequence
1. Day 0: email to the primary contact
2. Day 2 or 3: LinkedIn touch for the same contact or a second stakeholder
3. Day 5: follow-up email with a different angle or short example
4. Day 8 or 9: short close-the-loop follow-up
## Example email
```text theme={null}
Subject: [topic]
Hey [Name],
Saw you were engaging with [topic].
We hear that exact issue from [their company type] teams a lot, especially when [specific nuance].
Happy to send over the short version of what seems to work if useful.
```
## Common mistakes
* treating every like as a buying signal
* sending the same message to every stakeholder
* pitching features instead of the problem they engaged with
* ignoring account-level patterns when several people from one company are active
## What good looks like
* your best signals come from comments, repeat engagement, and company clusters
* hot signals outperform stale ones
* multi-threaded accounts outperform single-threaded outreach when the account fit is strong
For the broader framework, use [outbound to signal-based leads](/using-traxy/outbound-to-signal-based-leads).
# Outbound to signal-based leads
Source: https://docs.traxy.ai/using-traxy/outbound-to-signal-based-leads
Turn qualified leads and qualified engagements into better email and LinkedIn outreach.
Use this guide when traxy surfaces a qualified lead or qualified engagement and you want to turn that signal into a real conversation.
## Quick start
* Work the freshest signals first. Comments, shares, repeat engagement, and company clusters beat one-off reactions.
* Use the signal as context, not surveillance. Reference the topic unless the engagement was explicit and substantive.
* Start with an interest-based ask, not a meeting request.
* Use email for stronger, clearer signals and LinkedIn for lighter or more conversational first touches.
* Measure signal type, freshness, reply rate, and meeting rate every week so you know which signals are worth your team’s time.
## What makes signal-based outbound different
Signal-based outbound works because you already have a real reason to reach out. The lead engaged with a topic, post, or idea that matches your ICP.
That changes your job. You do not need to invent relevance. You need to:
* move while the signal is still fresh
* use the exact topic as your angle
* keep the message short and specific
* ask for a small next step
Treat the signal as context, not as surveillance. Mention only the detail that makes your outreach relevant.
## Start with the best signals first
Prioritize leads when you see:
* recent qualified engagement on a post tied closely to your offer
* repeat engagement from the same person
* strong ICP fit plus recent engagement
* comments or shares that show clear interest in the topic
* multiple engaged people from the same company
Deprioritize leads when you see:
* weak ICP fit
* old signals with no recent activity
* engagement on broad content with no clear business angle
* one-off low-context reactions you cannot turn into a relevant message
## Signal freshness and decay
How fast you move matters almost as much as what you say.
| Tier | Window | What it means | How to work it |
| - | - | - | - |
| Hot | 0-48 hours | The signal is still current and likely top of mind. | Reach out the same day or next business morning. Use the topic directly. |
| Warm | 3-7 days | Still relevant, but no longer immediate. | Send a clear first touch with one strong angle. |
| Cooling | 8-14 days | The signal is fading. | Reach out only if ICP fit is strong or the engagement was substantive. Reference the topic more broadly. |
| Cold | 15+ days | The signal is no longer timely on its own. | Treat it like cold outbound with context. Do not lean hard on the original action. |
If you are working signals older than two weeks, prioritize speed over polish on your next fresh signals. The stale ones are already losing their advantage.
## Conflicting signals
Not every lead is cleanly high or low priority. Use this rule set when fit and engagement do not line up.
| ICP fit | Signal strength | What to do |
| - | - | - |
| Strong | Strong | Highest priority. Move fast. Use the clearest channel for the context. |
| Strong | Light | Still worth pursuing. Soften the opener and reference the topic rather than the exact action. LinkedIn-first often works well here. |
| Weak | Strong | Proceed carefully. The interest is real, but the buying fit may not be. Check whether the engagement reveals a real use case before you spend too much time. |
| Weak | Light | Skip it. This is what deprioritize means in practice. |
## Reference the signal without sounding invasive
Use the signal to explain why your message is relevant. Do not use it to prove that you tracked every action.
A good rule:
* if the lead commented, shared, or engaged repeatedly, you can be more direct
* if the lead only gave a light reaction, reference the topic instead of the exact action
Better:
* You were engaging with a conversation on \[topic].
* Your comment on \[topic] stood out to me.
* It looked like \[topic] is relevant to your team right now.
Avoid:
* I saw you liked my post at 9:14 AM.
* I noticed every reaction you left on our content.
* I tracked your recent activity and wanted to reach out.
## Choose the right channel
### Use email when you want:
* more room for context
* a stronger business case
* an easy reply path
* a message that can stand on its own
### Use LinkedIn when you want:
* a lighter first touch
* to follow up on content or thought leadership
* to stay close to the topic they engaged with
* to warm up a future email conversation
### Use both when:
* the lead is a strong ICP match
* the signal is recent
* you can keep each touch short and different
Do not copy the same message into both channels.
## Use a simple workflow
1. Review the lead in traxy.
Check the ICP fit, the topic that triggered interest, and whether the signal is still fresh.
2. Pick one angle.
Choose one problem, one outcome, or one point from the content they engaged with.
3. Start with the lightest credible message.
If the signal is strong, email can work first. If the signal is lighter, LinkedIn is often a better first touch.
4. Follow up with new value.
Add a new example, insight, or question. Do not just ask whether they saw your last message.
5. Stop when the fit or interest is low.
Signal-based outbound works best when you stay selective.
## Email best practices
Use email when you want a clear, focused business message.
### Keep the message short
Short emails usually work better than long explanations. Keep the message easy to scan and centered on one idea.
A strong signal-based email usually includes:
* a short subject line
* a first sentence tied to the signal
* one clear problem or outcome
* a low-friction call to action
### Use an interest-based call to action
Your first ask does not need to be a meeting.
Better first asks include:
* open to seeing how other teams handle this?
* worth sending over the short playbook we use here?
* is this something your team is actively working on?
These asks are easier to answer than a direct calendar request.
### Keep deliverability clean
If you send outbound at volume, use a properly authenticated sending domain and keep complaint rates low. Platform rules for bulk email have become stricter, especially for Gmail and Yahoo inboxes.
If you run larger outbound programs, review the official sender guidance from Google and Yahoo before you scale.
### Example email framework
```text theme={null}
Subject: [topic]
Hi [First name],
You engaged with a post on [topic], so I thought I would reach out directly.
Teams like [their team or company type] usually run into [specific problem] when this becomes a priority. We help with [specific outcome].
Would it be useful if I sent over the short version of how we approach this?
```
If the signal was only a light reaction, soften the opener. For example:
```text theme={null}
You were following a conversation on [topic], so I thought I would reach out directly.
```
### Conversational version
Use this style when you want the message to feel more like a real note and less like a sequence.
```text theme={null}
Subject: [topic]
[First name] - saw you were engaging with [topic].
We keep hearing the same issue from [their company type] teams, especially when [specific nuance].
Happy to send over the short version of what seems to be working if useful.
```
### Make it stronger
* mention the topic, not every micro-signal
* use plain language
* keep the first email focused on one point
* sound like a person, not a sequence
## LinkedIn best practices
Use LinkedIn when you want a softer first touch around a topic the lead already engaged with.
### Keep connection requests light
If you are not connected yet, do not use the connection note as a full pitch.
Better connection notes:
* reference the topic briefly
* give a real reason to connect
* avoid a hard ask
Example:
```text theme={null}
Hi [First name], your take on [topic] caught my eye. We work with teams on [related outcome] and I thought it made sense to connect.
```
### Use direct messages for follow-up, not pressure
After you connect, send a short note that adds context or value.
Example:
```text theme={null}
Thanks for connecting. You were engaging with [topic], and we see a lot of teams hit [problem] there. Happy to share the short playbook we use if that would be useful.
```
### Stay within platform norms
Thoughtful invitations and relevant messages work better than high volume. LinkedIn also expects you to avoid spammy behavior on the platform.
## When not to reach out
Hold back when:
* the person engaged with a sensitive or emotional topic where a pitch would feel tone-deaf
* the signal came from someone who is clearly outside the buying path and there is no reasonable route to a decision-maker
* your team already contacted this person recently through another campaign or channel
* the engagement was clearly drive-by noise, such as a single reaction on a high-volume post with no stronger follow-through
Sometimes the right move is to keep monitoring instead of forcing a first touch.
## A practical starting sequence
Use this as a starting point, not a rule:
1. Day 0: email tied to the signal
2. Day 2 or 3: LinkedIn connection request or short DM
3. Day 5: email follow-up with a new angle, example, or resource
4. Day 8 or 9: LinkedIn follow-up with one simple question
5. Day 12: close the loop with a short final message
Keep each touch different. Every message should earn its place.
## Benchmarks and what good looks like
Use benchmarks to compare signal types and process quality, not to chase vanity numbers.
* Use your first 30 days to set an internal baseline by signal type and freshness tier.
* Signal-based outreach should beat your cold outbound baseline on both reply quality and meeting quality.
* Hot signals should outperform warm and cooling signals.
* Comments, shares, repeat engagement, and multi-person company engagement should outperform one-off reactions.
* Your team should work hot signals within the same day or next business day, and all active signals within 48 hours.
* Signals older than two weeks should usually perform more like cold outbound than like fresh signal-based outreach.
If those patterns are not showing up, your signal selection or messaging is off.
## Measure signal quality over time
Close the loop on every signal you work.
* Tag outreach by signal type, such as comment, repeat engagement, share, or company cluster.
* Track reply rate by signal type and freshness tier.
* Track meeting rate by signal type and freshness tier.
* Review which signals create replies but not meetings. Those signals may show curiosity without real buying fit.
* Drop signals that repeatedly underperform. Not every engagement pattern deserves your team’s time.
## Team coordination
If multiple people work the same accounts, coordinate before you send.
* Assign ownership by account or by signal type.
* Do not let two people from your team reach out to the same person about the same signal.
* When several people from one target company engage, coordinate the motion by seniority and role.
* Use a shared queue, CRM owner, or clear status tags so everyone knows which lead is already being worked.
## Ideas to test
Try these variations:
* segment by signal type, such as comments, repeat engagement, or multi-person company engagement
* change the first call to action from meeting-based to interest-based
* send email first for strong ICP matches and LinkedIn first for lighter signals
* build different angles for thought leadership posts versus product or problem posts
* prioritize repeat engagers for faster follow-up
## Mistakes to avoid
Avoid these common problems:
* leading with a generic pitch instead of the signal
* mentioning small actions in a way that feels invasive
* asking for too much in the first touch
* copying the same message into email and LinkedIn
* following up without adding anything new
* working weak-fit leads just because they engaged once
## Suggested outbound principles for traxy users
Use traxy to help you stay selective.
* Start with strong ICP matches, not every engaged person.
* Match the outreach angle to the post or topic that created the signal.
* Move faster on repeat engagement and company clusters.
* Use manual review when the signal is interesting but not yet clear enough for automatic action.
## Choose a playbook
Use the playbook that matches your motion:
Match common signals to the right first move, channel, timing, and opener.
Convert engagement on your own LinkedIn posts into conversations.
Work signal-based leads in multi-stakeholder software deals.
Lead with expertise and trust when selling services.
Work pre-event, during-event, and post-event signals without losing the window.
## Further reading
* [Google Workspace Admin Help: Email sender guidelines FAQ](https://support.google.com/a/answer/14229414)
* [Yahoo: Sender Best Practices](https://senders.yahooinc.com/best-practices/)
* [LinkedIn: Professional Community Policies](https://www.linkedin.com/legal/professional-community-policies)
* [Gong: Does cold email even work any more?](https://www.gong.io/blog/does-cold-email-even-work-any-more-heres-what-the-data-says)
* [Gong: Cold email statistics](https://www.gong.io/blog/cold-email-stats)
# How qualification works
Source: https://docs.traxy.ai/using-traxy/qualification
Understand how traxy turns ICP matches and buyer signals into qualified leads.
Qualification decides whether a person should become a lead in your workspace.
traxy combines your active ICP, minimum match, company exclusions, and a supported discovery signal. It saves the person as a qualified lead when the result meets the workspace rules.
## What traxy evaluates
Your ICP describes the people and companies you want:
* job titles
* departments
* seniority
* locations
* company size
* industries
* revenue
* funding
* keywords and niches
* company or product summary
The **Minimum ICP match** on Dashboard decides how strong the match must be. Raising it makes qualification stricter. Lowering it includes more borderline matches.
## Where qualified leads come from
### Agent
Agent scans profiles that match the approved ICP. It saves the people who meet the current qualification rules.
### Watchlist and Post Signals
Watchlist and Post Signals evaluate people who like, comment on, or repost a monitored LinkedIn post.
Watchlist runs one free initial discovery when you first add a profile. It then manages a required sliding window of the five most recent posts published after the profile was added.
Manual **Find Leads** can qualify another LinkedIn post after traxy reserves the required credits.
## What prevents a lead
A person does not enter the active lead list when:
* the ICP match is below the workspace minimum
* the person's company domain is on the Blocklist
* the person is already handled by deduplication
* required qualification access or credits are unavailable
* you previously moved the lead to another workflow state
Existing **Clients**, **Snooze**, **Done**, and **Bad fit** leads stay in their respective views. traxy does not create another active copy of the same person.
## Give qualification feedback
Use **Mark as good fit** or **Mark as bad fit** in Leads. Select the applicable reasons and add a note when context matters.
This feedback helps traxy improve later qualification. **Mark as done**, **Snooze lead**, and **Mark as client** are workflow actions. They do not mean the ICP score was wrong.
## Understand credit settlement
Most qualification uses 1 credit for each unique billable profile in the current billing window. Repeated engagement from the same person is deduplicated for that window.
Manual post requests reserve the exact available credits before work starts. The final settlement reflects the unique profiles that produced billable results.
Agent uses a different rule after its trial allowance. It charges each unique profile scanned in the billing window, even when that profile does not become a qualified lead.
Contact enrichment is separate from qualification:
* a newly saved email uses 3 credits
* a newly saved phone number uses 5 credits
## Review the result
Open a lead to review its ICP match, qualification summary, source, and engagement history. Use those details before you classify, enrich, export, or route the lead.
Change the people and company criteria.
Review results and give fit feedback.
# Signal cheat sheet
Source: https://docs.traxy.ai/using-traxy/signal-cheat-sheet
Map common signal types to the right channel, timing, and first-touch angle.
Use this page as a fast reference when you know a lead engaged but you need to decide what to do next.
## How to use this sheet
Start with three questions:
1. How strong is the ICP fit?
2. How fresh is the signal?
3. Does the signal show real interest or just light awareness?
Then use the table below to choose the first move.
| Signal | What it usually means | Best first move | Channel | Timing | Example opener |
| - | - | - | - | - | - |
| Comment on your post or a relevant post | Active interest and clear topic relevance | Reach out directly with one tight angle | LinkedIn or email | Same day or next business day | Your comment on \[topic] stood out to me. |
| Share or repost | Stronger endorsement than a like | Thank them, then bridge to the problem or takeaway | LinkedIn first | Same day or next business day | Saw you shared \[topic]. It seems especially relevant for \[their team type]. |
| Repeat engagement across multiple posts | Ongoing interest, not a one-off | Reference the broader theme, not every action | Email or LinkedIn | Within 48 hours of the most recent signal | You have been engaging with a few conversations around \[theme], so I thought I would reach out directly. |
| Multiple people from one company engage | Potential account-level interest | Coordinate a multi-threaded approach | Email for senior contacts, LinkedIn for lighter touches | Within 48 hours | A few people from \[company] have been engaging with \[topic], so I thought I would reach out with one practical angle. |
| Single like or light reaction | Light awareness, weak standalone signal | Work only if ICP fit is strong | Usually LinkedIn | Within 48 hours if you work it at all | It looks like \[topic] may be relevant to your team right now. |
| Old signal older than 14 days | Context, but no longer urgency | Treat like cold outbound with context | Email or LinkedIn | When capacity allows | I know this is not brand new, but \[topic] still looked relevant enough to reach out. |
| Event session post or recap | Topic interest tied to a time-bound moment | Reference the exact session or takeaway | LinkedIn first, then email | During the event or within 48 hours after | Saw your post about \[session topic] at \[event]. |
| Thoughtful comment on your own content | Warmest content-led signal | Reply publicly first, then follow up privately | LinkedIn | Public reply within 24 hours, DM soon after | Really appreciated your take on \[topic]. |
## Fast rules
* Comments, shares, repeat engagement, and company clusters beat one-off reactions.
* If the engagement was light, reference the topic instead of the exact action.
* If the signal is old, make the topic do the work. Do not lean on the stale action.
* If you cannot explain why the signal matters in one sentence, do not reach out yet.
## What to skip
Skip or hold when:
* fit is weak and the signal is weak
* the person was already contacted recently
* the engagement came from a noisy, high-volume post with no follow-through
* the topic is sensitive enough that outreach would feel opportunistic
For the full framework, use [outbound to signal-based leads](/using-traxy/outbound-to-signal-based-leads).
# Watchlist
Source: https://docs.traxy.ai/using-traxy/watchlist
Monitor LinkedIn profiles and qualify people who engage with their posts.
Use Watchlist to monitor people whose LinkedIn audiences matter to your workspace.
## Choose a relationship
Watchlist supports:
* **Competitor**
* **Teammate**
* **Influencer**
* **Investor**
* **Custom**
Use **Custom** for a reusable relationship such as client, partner, or customer.
## Add profiles
1. Open **Watchlist**.
2. Click **Add LinkedIn Profile**.
3. Paste a LinkedIn profile URL.
4. Verify the profile.
5. Confirm the relationship and company.
6. Add the profile.
Use batch mode to paste up to 20 LinkedIn profile URLs at once. The 20-URL bound applies to one verification request, not to the size of your Watchlist.
Watchlist profiles are unlimited. A separate limit can apply when a relationship requires a competitor company.
## Understand the first discovery
A profile's first successful addition creates one free initial discovery.
traxy freezes up to five recent posts and examines them until it finds five new qualified leads or reaches the end of the frozen window.
The discovery belongs to the profile:
* adding a duplicate does not create another discovery
* restoring a removed profile does not create another discovery
* pausing or removing the profile suspends it
* resuming or restoring the profile continues the same discovery
Qualification after this one-time discovery uses the workspace credit balance.
## Understand ongoing qualification
After you add a profile, traxy manages the five most recent posts published from that point forward.
This is a sliding trailing-five window. It is always on for active Watchlist monitoring and cannot be disabled or reduced. Already examined posts process only new, deduplicated engagement.
Use manual **Find Leads** in [Post Signals](/using-traxy/content-calendar) for a post outside the managed window.
## Use tabs and summary cards
Use **All Profiles**, **Competitors**, **Teammates**, **Influencers**, **Investors**, and **Custom** to narrow the table.
The summary cards show:
* **All Profiles Monitored**
* **Qualified Posts**
* **Engagements**
* **Qualified leads**
Use **Monitor** and **Archived** to move between active and removed profiles.
## Review the table
Each row can show the profile, relationship, company, qualified posts, qualified leads, **CPL**, state, and date added.
**CPL** means credits used per qualified lead in the current billing window.
Open a profile to review:
* audience ICP match
* qualified posts and leads
* credits used in the current billing window
* recent top leads
* tracked posts and qualification status
You can pause, resume, remove, or restore a manually added profile. Some teammate profiles can be created from workspace member context and may have different controls.
## Use recommendations
**Recommended for you** can suggest profiles based on your workspace context. Review the relationship and expected signal before you add one. Dismiss a recommendation when it is not useful.
High-engagement profiles can produce more qualification work. Review **Post Signals** and credit usage when you want to understand the cost of a profile's activity.
# Profiles & Users
Source: https://docs.traxy.ai/using-traxy/workspace-and-team
Manage members, roles, invites, and account settings in traxy.
Use Profiles & Users and the settings area to manage who has access and how your team works inside traxy.
## Create a workspace
When you create a new workspace, traxy makes you the **Owner**.
## Invite members
Owners and admins can invite members from:
* the sidebar action for inviting a team member
* **Settings** > **Profiles & Users**
When you send an invite, choose the access level that fits the person joining:
* **Admin** for workspace setup and management
* **Member** for day-to-day work in the product
In the members view, you can track statuses such as:
* **Active**
* **Invite Pending**
* **Disabled**
## Manage roles
traxy uses workspace roles to control access.
* **Owner** has full workspace control.
* **Admin** can manage key workspace settings and members.
* **Member** works inside the workspace without full admin access.
If your role allows it, you can update roles or remove access from the same members screen.
Removing access disables that member immediately.
## Update profile and company settings
Use **Settings** to manage personal and workspace information such as:
* **Profile**
* **Company**
* **Security**
* **Billing**
* **Blocklist**
* **Profiles & Users**
These settings help keep your workspace accurate as your team changes.
Use **Company** when you want to review the confirmed company record that powers your workspace.
Use **Blocklist** when you want to exclude specific company domains from future leads.
# Leads: High Intent & Warm Leads
Source: https://docs.traxy.ai/videos/leads-high-intent-and-warm-leads
How traxy turns LinkedIn engagement into a daily list of warm, high-intent leads.
Learn how traxy finds high-intent leads on LinkedIn by connecting who fits your ICP with what they're actually engaging with and how recently they were active. You'll see real leads and the signals behind them, and how to use that context to decide who to reach out to and what to say.
A hundred people can engage with your content — only a few are actually ready to buy. Here's how traxy tells them apart:
* **How signals work** — how traxy connects your ICP to real LinkedIn engagement to flag intent.
* **Real lead examples** — actual leads in a traxy account and the signals behind them.
* **Why activity matters** — why recent activity is what makes a lead worth reaching out to now.
* **ICP and buying signals** — how your ICP and signal definitions shape which leads traxy finds.
* **The agent, watchlist & post signals** — how these work together to keep surfacing the right leads.
* **Research and outbound** — how to turn a lead's context into who to contact and what to say.
By the end, you'll know how to read a lead's signals and turn that context into a next step — reaching out to the right person, at the right moment, with the right message.
# Watchlist & Agent: Strategy
Source: https://docs.traxy.ai/watchlist-and-agent-strategy
Set up your watchlist and let the Agent work your strategy.
Learn how to build your watchlist in traxy and set your agent's budget around the audiences that matter most to your business. You'll see how to track competitors, teammates, your own profile, and people who reach the same buyers — and how to read the signals behind their content so you know who's actually worth following up with.
More engagement doesn't always mean more relevant leads — here's how to make your watchlist and agent budget work together:
* **Organize your watchlist** — group tracked profiles with tags so you know why each one is there.
* **Your content signals** — how engagement with case studies and other content should shape your outreach.
* **Different sources, different follow-ups** — why a lead from your own content needs a different approach than one from a competitor's or an influencer's.
* **Agent and budget** — set how many profiles the agent scans per day, based on the audiences you actually want covered.
* **Review credit efficiency** — check agent activity regularly so you're not spending credits on low-fit audiences.
By the end, you'll have a watchlist built around the right people and an agent budget spending its credits where the signal is strongest.