Oktopost and Clay Integration Guide

Turn social engagement into actionable Marketing Automation Platform (MAP) contacts when leads do not yet have an email address in Oktopost. This guide walks through pulling social leads from Oktopost into Clay, enriching them with work email and firmographic data, cross-checking your MAP for duplicates, and routing only net-new leads to a Master Enrichment Table ready for MAP entry.

Prerequisites

• Oktopost account with API access
• Clay account on a paid plan (required for enrichment columns)
• Access to your MAP or CRM for the final sync step

How the Workflow Fits Together

Authentication

All Oktopost API requests use HTTP Basic Authentication. Your username is your Account ID and your password is your API Key. Find both in Oktopost under Settings > My Profile > API.

Authentication in Clay

Clay does not auto-encode Basic Auth credentials. You must Base64-encode them manually and pass the result as an Authorization header.

1. Go to base64encode.org
2. Enter your credentials in the format: AccountId:APIKEY
3. Click Encode and copy the result
4. In Clay's header field, enter: Basic <your-encoded-string>

Rate Limits

Part 1 — Staging Table: Pulling Leads from Oktopost

1.1 Set Up the HTTP API Source in Clay

In Clay: Actions > View all sources > Import data from an HTTP API

Headers (saved in account)

Query Parameters

1.2 Map Columns from the API Response

The /v2/lead list response returns lead data at the top level of each Items entry. Map these fields by clicking each column header > Edit Column > type / to select the source field.

1.3 LinkedIn Profile Column (Formula)

The Profiles array in each lead record contains social network URLs. The order is not fixed. Use this formula to scan up to five entries and return the first LinkedIn URL found.

In Clay: Click the column header > Edit Column > click the cog icon > select Formula, then paste:

{{Profiles}}?.[0]?.Network == "LinkedIn" ? {{Profiles}}?.[0]?.Url :
{{Profiles}}?.[1]?.Network == "LinkedIn" ? {{Profiles}}?.[1]?.Url :
{{Profiles}}?.[2]?.Network == "LinkedIn" ? {{Profiles}}?.[2]?.Url :
{{Profiles}}?.[3]?.Network == "LinkedIn" ? {{Profiles}}?.[3]?.Url :
{{Profiles}}?.[4]?.Network == "LinkedIn" ? {{Profiles}}?.[4]?.Url : ""

1.4 Already Synced to MAP Column (Formula)

The RemoteLeads array in each lead record indicates whether the lead is already linked to a connected Oktopost integration. An empty array means the lead has not been synced. Use this as an initial filter before the full MAP lookup:

{{RemoteLeads}}?.length > 0 ? "true" : "false"

1.5 Staging Table Settings

Open Table Settings: click the cog icon in the bottom right of the table.

Part 2 — Clay Enrichment

This is the core value step. Clay uses the LinkedIn profile URL and other available data to find work email addresses and firmographic details for each lead. The specific enrichment providers and waterfall logic are configured by you, but the following points are essential for this workflow.

• Email is the prerequisite for MAP entry. A lead cannot be created in most MAPs without an email address. The enrichment step is what converts social leads without emails into actionable MAP contacts.
• Run enrichment before the MAP cross-check. Only attempt to route a lead to the MAP after Clay has found an email. Add a condition to the MAP routing column: Only run if Email is not empty.
• LinkedIn URL is the most reliable enrichment key. The LinkedIn profile URL extracted in Part 1.3 is what most Clay enrichment providers use to look up a person. Ensure this column is populated before running enrichment.
• Leads without an email after enrichment should not proceed. If Clay cannot find an email for a lead, that lead should remain in the staging table. The Only run if condition on the MAP Lookup column (Part 3) enforces this.

Part 3 — MAP Cross-Check and Routing

Once a lead has been enriched and has a confirmed email, this step checks whether they already exist in your MAP. Only net-new leads proceed to the Master Enrichment Table.

3a MAP Lookup Column

Add a lookup column that queries your Master Enrichment Table to confirm whether the lead already exists there.

In Clay: Click Add enrichment > search for Lookup Single Row in Other Table

Record Found — lead already exists, do not re-send. No Record Found — lead is net-new, proceed.

3b Send to Master Enrichment Table

In Clay: Click Add enrichment > search for Send Table Data > select Send Row

Select the following fields and map each to the corresponding column in the Master Enrichment Table:

• LeadId
• FirstName
• LastName
• Email (enriched)
• LinkedInProfile
• Any additional Clay enrichment columns (company, job title, and others)

Part 4 — Master Enrichment Table Settings

The Master Enrichment Table is the customer-owned table that holds enriched, confirmed, net-new leads ready for MAP creation.

Part 5 — MAP / CRM Handoff (Your Step)

Once a lead exists in the Master Enrichment Table and has been enriched, you control how it flows into marketing automation. Common approaches:

• Push to HubSpot, Marketo, Eloqua, Pardot, or Dynamics via Clay's native connectors
• Use a Clay HTTP API export column to call the MAP's API directly
• Use Make or n8n to watch the Master Enrichment Table and trigger MAP workflows

API Quick Reference

Oktopost Endpoints Used in This Workflow

Base URLs

API Response — List Leads Structure

{
  "Result": true,
  "Items": [
    {
      "Id": "0ld000000000001",
      "FirstName": "John",
      "LastName": "Doe",
      "Email": "john@example.com",
      "Phone": null,
      "IsTracked": true,
      "Profiles": [
        { "Network": "Instagram", "Url": "https://instagram.com/..." },
        { "Network": "Twitter",   "Url": "https://twitter.com/..."  }
      ],
      "RemoteLeads": [
        { "IntegrationType": "hubspot", "IntegrationID": "...", ... }
      ]
    }
  ]
}

Known Constraints and Status