---
title: PersistIQ API Integration on Truto
slug: persistiq
category: CRM
canonical: "https://truto.one/integrations/detail/persistiq/"
---

# PersistIQ API Integration on Truto



**Category:** CRM  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 13 tools for PersistIQ that AI agents can call directly.

- **create_a_persist_iq_campaign_lead** — Add up to 100 leads to a campaign (more than 100 returns 400). Leads already in the campaign come back under errors ("Lead has already been taken"); the others are added. Required: campaign_id, and leads or lead_id.
- **delete_a_persist_iq_campaign_lead_by_id** — Remove a lead from a campaign. The id is the lead ID (l_...). Required: campaign_id, id.
- **list_all_persist_iq_campaigns** — List campaigns with their send statistics, optionally only those a lead belongs to, owned by a user, or with a given name. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **list_all_persist_iq_dnc_domains** — List Do Not Contact domains: emails to addresses at these domains are not sent without manual approval. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **create_a_persist_iq_dnc_domain** — Add a Do Not Contact domain, so emails to addresses at that domain need manual approval. Required: name.
- **list_all_persist_iq_events** — List account activity events (lead created/updated, campaign changes, messages sent, replies, opens, clicks, bounces), optionally filtered by group, campaign, lead, user and time range. message_received means the lead replied. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **list_all_persist_iq_lead_fields** — List all lead fields (built-in and custom) of the company. Their name is the key in a lead's data.
- **list_all_persist_iq_lead_statuses** — List all lead statuses of the company (e.g. engaged, working, unresponsive).
- **list_all_persist_iq_leads** — List leads, 100 per page, optionally filtered by status name or update time. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **get_single_persist_iq_lead_by_id** — Get a single lead by ID (e.g. l_1abc). Required: id.
- **create_a_persist_iq_lead** — Create up to 10 leads per call. A lead whose email already exists is skipped (dup = skip, the default) or updated (dup = update). The response lists the created leads and, with status = error, the leads that failed (e.g. blank email); the others are still created. Required: leads (each with email).
- **update_a_persist_iq_lead_by_id** — Update a single lead: change its status (by name or status_id), mark it bounced or opted out, or set built-in and custom attributes in data. Required: id.
- **list_all_persist_iq_users** — List all non-archived users of the company. Use a user's id as creator_id on leads.create, and default_mailbox_id as mailbox_id on campaign_leads.create.

## How it works

1. **Link your customer's PersistIQ account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach PersistIQ.** The Proxy API is a 1-to-1 mapping of the PersistIQ API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Push prospects from your lead database into PersistIQ campaigns** — If you run a prospecting or data enrichment product, let users send sourced contacts straight into their active PersistIQ campaigns instead of exporting CSVs. This closes the loop between finding a lead and starting outreach inside your product.
- **Automate DNC compliance from your CRM or ABM platform** — When accounts in your platform are marked Closed-Won, churned, or opted out, automatically add their domains to the user's PersistIQ Do Not Contact list. This protects your customers from embarrassing cold outreach to existing accounts.
- **Halt sequences based on cross-platform signals** — If you're building an AI sales assistant or inbox manager, detect replies, booked meetings, or disinterest from other channels and immediately remove leads from PersistIQ campaigns. Prevents awkward follow-ups after a prospect has already engaged.
- **Log PersistIQ engagement into your system of record** — For niche CRMs, ATSes, or analytics platforms, poll PersistIQ events (opens, clicks, replies, bounces) and attach them to the right contact or account timeline. Keeps your product the single source of truth for engagement history.
- **Enrich and update leads from your product's data** — When your platform learns new information about a contact (title changes, firmographic updates, intent signals), push updates to the matching PersistIQ lead so SDRs always work from fresh data.

## What you can build

- **"Send to PersistIQ Campaign" action** — Let users select a PersistIQ campaign and mailbox from a dropdown and enroll selected leads directly from your UI in a single batched flow.
- **Automated DNC domain sync** — Trigger `create_a_persist_iq_dnc_domain` when accounts are marked as customers, churned, or unsubscribed in your platform to enforce suppression automatically.
- **Reply and engagement webhooks** — Poll `list_all_persist_iq_events` on a schedule, filter for message_received, opens, clicks, and bounces, and emit normalized events into your product's activity feed.
- **Bi-directional lead status sync** — Map your internal lifecycle stages to PersistIQ lead statuses and keep them in sync using `list_all_persist_iq_lead_statuses` and `update_a_persist_iq_lead_by_id`.
- **Campaign exit automation** — When a prospect books a meeting or replies through another channel in your product, call `delete_a_persist_iq_campaign_lead_by_id` to remove them from active sequences instantly.
- **Custom field mapping UI** — Use `list_all_persist_iq_lead_fields` to let your users map their internal fields to PersistIQ's built-in and custom lead fields during integration setup.

## FAQs

### How does authentication to PersistIQ work through Truto?

PersistIQ uses API key authentication. Truto handles the credential collection, secure storage, and injection into every request, so your end users simply paste their PersistIQ API key once during the connect flow.

### How does Truto handle duplicate leads when pushing to PersistIQ?

PersistIQ's lead creation endpoint supports native duplicate handling via `dup = skip` or `dup = update` parameters. You can pass these through Truto's `create_a_persist_iq_lead` tool, so deduplication logic stays with PersistIQ rather than something you have to build.

### Can we enroll multiple leads into a campaign in one call?

Yes. `create_a_persist_iq_campaign_lead` accepts up to 100 leads per call, and `create_a_persist_iq_lead` supports up to 10 leads per call. Truto exposes these batching limits directly so you can efficiently handle bulk enrollment.

### How do we get near real-time replies and opens from PersistIQ?

PersistIQ exposes engagement data via its events endpoint. Through Truto's `list_all_persist_iq_events` tool you can poll on a schedule with a time range filter to pick up message_received, open, click, and bounce events for downstream automation.

### Does the integration support custom lead fields?

Yes. Use `list_all_persist_iq_lead_fields` to discover both built-in and custom fields configured in a user's PersistIQ account, then map and write to them via `create_a_persist_iq_lead` or `update_a_persist_iq_lead_by_id`.

### Can we programmatically manage the Do Not Contact list?

Yes. `list_all_persist_iq_dnc_domains` and `create_a_persist_iq_dnc_domain` give you full control to read and add suppressed domains. Note that PersistIQ requires manual approval before DNC domains take effect for future sends.

### What if we need a PersistIQ capability that isn't in Truto's tool list yet?

Truto builds integrations on request and can extend PersistIQ coverage to additional endpoints. Reach out with the specific workflow you need and the tool can be added to your workspace.
