Aimfox x Clay Integration | Aimfox Help Center

You can connect your Clay workspace to Aimfox using Clay's HTTP API integration and your Aimfox API key.

This lets you call any Aimfox API endpoint directly from a Clay table - pulling leads, managing campaigns, enriching rows with LinkedIn data, and more, without needing a native integration.

For a full list of available endpoints, refer to our API documentation.

Prerequisites

An active Clay account (any paid plan)
An active Aimfox account with API access
An Aimfox API key: go to Settings → API Keys in your Aimfox dashboard

Setting up your API key in Clay

Before making any requests, save your Aimfox API key as a Clay integration account so it's stored securely and reusable across tables.

In Clay, open the HTTP API enrichment or source configuration.
Under Account, click Add new account.
Give it a name (e.g. Aimfox).
In the Authorization header field, enter Bearer YOUR_API_KEY
Save the account. You can now select it whenever you add a new Aimfox HTTP API enrichment.

Never paste your API key directly into the headers field of a table column - always use a saved account to keep your credentials secure.

Making requests: enrichment vs. source

Clay's HTTP API works in two modes. Choose the one that fits your use case:

Enrichment - use this when you already have rows in a Clay table and want to add Aimfox data to each one (e.g. fetch lead details for a list of LinkedIn URLs).
Source - use this when you want to pull a list from Aimfox to create a new Clay table (e.g. import all recent leads into Clay).

HTTP API enrichment setup

Use this to enrich existing rows with data from Aimfox - for example, fetching campaign details or lead information row by row.

Open your Clay table and click Add enrichment.
Search for and select HTTP API.
Select your saved Aimfox account.
Configure the request.

Request configuration:

Method: GET for retrieving data, POST for creating records

Endpoint URL: The Aimfox API endpoint you want to call. All endpoints use the base URL:

https://api.aimfox.com/api/v2

For example, to get details for a specific lead:

https://api.aimfox.com/api/v2/leads/{{lead_id}}

Replace {{lead_id}} with a reference to the relevant column in your Clay table (e.g. /Lead ID Column).

For POST requests, add your JSON body. Use /Column Name references to map table data dynamically. String values must be wrapped in quotes:

{   
   "profile_url": "/LinkedIn URL Column",   
   "campaign_id": "/Campaign ID Column" 
}

Also don't forget to add the following header:

Key	Value
`Content-Type`	`application/json`

Set a results path if the data you need is nested inside the response (e.g. data.lead) and then click Test to run on a single row, verify the output, then run on your full table.

HTTP API as source setup

Use this to pull a list from Aimfox directly into a new Clay table - for example, importing all recent leads or all campaigns.

Click Actions → View all sources.
Search for and select Import data from an HTTP API.
Select your saved Aimfox account.
Set the Method to GET and enter the endpoint URL. For example, to import recent leads:

https://api.aimfox.com/api/v2/leads/recent

In Results path, specify where the array of records sits in the response (e.g. leads or data). Check the Aimfox API docs for the exact response structure of each endpoint.
Preview the response, map the fields to Clay columns, and import.

Note: Clay's HTTP API source does not currently support pagination. You'll receive only the first page of results from the API response.

Common Aimfox endpoints for Clay

Here are some useful starting points. All endpoints use the base URL https://api.aimfox.com/api/v2.

Action	Method	Endpoint
List all accounts	GET	`/accounts`
List all campaigns	GET	`/campaigns`
Get a specific campaign	GET	`/campaigns/{campaign_id}`
List recent leads	GET	`/leads/recent`
Get a specific lead	GET	`/leads/{lead_id}`
Search leads	GET	`/leads/search`
Add profile to campaign	POST	`/campaigns/{campaign_id}/targets`
List conversations	GET	`/conversations`
List templates	GET	`/templates`

Refer to the Aimfox API documentation for the full list of endpoints, required parameters, and response structures.

Rate limits

The Aimfox API allows a maximum of 60 requests per minute. Configure rate limiting in Clay to stay within this:

In the HTTP API enrichment settings, scroll to Rate limiting.
Set Request limit to 60 and Duration to 60000 ms.

This ensures Clay won't exceed the limit when running enrichments on large tables.

Example: Pushing leads with custom variables to Aimfox campaigns

Here's one of our most common use-cases. Learn how to connect your Clay table with an Aimfox campaign and push all new table entries to the campaign.

We're using table rows as custom variables in the campaign for maximum personalization.

Tips

Test on one row first before running on your full table to catch configuration errors early and avoid wasted credits.
Use conditional runs to only trigger the enrichment when required columns (like Lead ID or Campaign ID) are populated.
Use field paths to extract only the data you need from the response rather than returning the entire object.
Save your setup as a template after a successful configuration so you can reuse it in other Clay tables.

Need Help?

Visit our API Docs for technical reference: https://docs.aimfox.com/
Reach out to us on the Live Chat for 1:1 help setting up your workflow
We'll be adding tutorials and templates soon - let us know what you'd like to see!