> ## Documentation Index
> Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate Dripify LinkedIn Outreach With Agents

> Let sales agents read Dripify campaigns and leads, add leads to campaigns, and send LinkedIn messages. The gateway keeps your API key out of the agent.

## Overview

OneCLI connects AI agents to [Dripify](https://dripify.com) with an API key. Agents can read campaigns and their statistics, look up leads, read LinkedIn conversations, and act on them: add leads to a campaign, tag them, or send a message. The gateway injects the key into every request, so your agent never sees it.

This suits sales agents that already work your pipeline: check who replied, pull a lead's history before a call, or move a promising lead into the right campaign.

Connecting takes about a minute.

> [!NOTE]
>
> Dripify's Open API is available on its **Advanced** and **Pro** plans only.

## What you will set up

* A Dripify API key (Advanced and Pro plans)
* Automatic key injection on Dripify API requests
* Per-agent, per-tool access, such as approval before messages go out

## Connect Dripify

**1. Generate an API key in Dripify**

In Dripify, open **Settings** > **Integrations**, find the **API Key** block, and select **Generate**.

![Dripify Settings, Integrations tab, showing the API Key block with a masked key and the Copy and Revoke buttons.](https://mintcdn.com/chartdbinc/u_wWi5rrEaqCMZx-/images/integrations/dripify/dripify-api-key.png?fit=max\&auto=format\&n=u_wWi5rrEaqCMZx-\&q=85\&s=cf8750873d81b72c528d1970ec01804a)

The API Key block in Dripify's Integrations settings.

Copy the key right away and keep it private. It gives full access to your Dripify account's data through the API.

**2. Paste it in OneCLI**

In the OneCLI dashboard, open **Connections** > **Dripify**, paste the key into **API key**, and select **Connect Dripify**.

![OneCLI connect window for Dripify, showing the setup guide link, the API key field with a hint to go to Settings, Integrations, API Key, and the Connect Dripify button.](https://mintcdn.com/chartdbinc/u_wWi5rrEaqCMZx-/images/integrations/dripify/onecli-connect-dripify.png?fit=max\&auto=format\&n=u_wWi5rrEaqCMZx-\&q=85\&s=38ea9dcbd5624cba2650e6e4c61b8b19)

The Dripify connect window in OneCLI.

OneCLI checks the key with Dripify before saving it, so a wrong or revoked key is rejected right away.

> [!TIP]
>
> Running outreach for more than one Dripify account? Connect each account's key separately, and tell them apart with the **Connection label** under **Advanced**.

## What agents can do

| Area | What agents can do |
| - | - |
| **Campaigns** | List campaigns, their lead lists, and their statistics |
| **Leads** | List and filter leads, look one up by email or LinkedIn profile URL, and read its details and activity |
| **Conversations** | Read a lead's LinkedIn conversation and its messages |
| **Teams** | List teams and their members |
| **Tags and fields** | List, create, apply, and remove tags, and set custom field values on leads |
| **Outreach** | Add leads to a campaign or lead list, and send a message in a lead's existing LinkedIn conversation |

> [!NOTE]
>
> Dripify limits each key to 60 requests a minute and 5,000 a day. Past that, Dripify answers `429` with a `Retry-After` header, and the agent should wait that long before retrying.

## Quick example

No `X-Api-Key` header is needed, the gateway adds it:

```bash theme={null}
# Your campaigns
curl -s "https://api.dripify.com/v1/open-api/campaigns"

# Find a lead by LinkedIn profile URL
curl -s -X POST "https://api.dripify.com/v1/open-api/leads/search" \
  -H "Content-Type: application/json" \
  -d '{"linkedinUrl": "https://www.linkedin.com/in/jane-doe"}'
```

For every endpoint and parameter, see the [Dripify API reference](https://api.dripify.com/).

## Controlling access

[Grant](https://onecli.sh/docs/guides/agent-access.md) the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what's blocked.

Outreach reaches real people under your name. A good default is to let agents read campaigns, leads, and conversations freely, and put **Send a LinkedIn message** and **Add leads to a campaign** behind approval. Adding leads to an active campaign starts messaging them, so it carries the same weight as sending.

Organization [rules](https://onecli.sh/docs/guides/rules.md) add guardrails on top. A blocked request never reaches Dripify.

To disconnect, remove the connection in **Connections** > **Dripify**, then revoke the key in Dripify under **Settings** > **Integrations** > **API Key** > **Revoke**.

## FAQ

> [accordion] How do I rotate my Dripify API key?
>
> Generate a new key in Dripify under **Settings** > **Integrations**, then paste it into **Connections** > **Dripify**. Agents pick up the new key automatically.

> [accordion] How do I keep the key out of the agent's context?
>
> Store it in OneCLI. The gateway injects it at the proxy, so the agent never holds a key with full access to your Dripify data. See [How it works](https://onecli.sh/docs/how-it-works.md).

> [accordion] Can I connect more than one Dripify account?
>
> Yes. Connect each account's key separately and tell them apart with the **Connection label** under **Advanced**.

> [accordion] Can I review LinkedIn messages before they're sent?
>
> Yes. Set message sending to need approval when you [grant](https://onecli.sh/docs/guides/agent-access.md) the connection.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.