Skip to main content
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

API

Create keys for direct REST access to traxy data.

Claude

Connect Claude web, desktop, or Claude Code with OAuth.

Codex

Connect ChatGPT, the Codex app, IDE extension, or CLI with OAuth.

Ordinal

Give Ordinal aggregate audience access with a dedicated key.

​
Lead delivery and audiences

Slack

Send qualified lead alerts to a Slack channel.

HubSpot

Create or update CRM contacts and companies.

Webhook

Send signed qualified lead events to your endpoint.

Zapier

Start a Zap from qualified lead events.

Clay

Send qualified lead events to a Clay webhook.

n8n

Start an n8n workflow from qualified lead events.

HeyReach

Send qualified leads to a campaign or lead list.

Meta Ads

Export qualified leads as a value-based audience CSV.

​
Choose manual or automatic delivery

Slack, HubSpot, 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.