Skip to main content

Overview

Buckle connects AI agents to Dripify 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.
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.

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 Buckle

In the Buckle dashboard, open Settings > Apps > Dripify, paste the key into API key, and select Connect Dripify.
Buckle 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.

The Dripify connect window in Buckle.

Buckle checks the key with Dripify before saving it, so a wrong or revoked key is rejected right away.
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

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:
For every endpoint and parameter, see the Dripify API reference.

Controlling access

Grant 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 add guardrails on top. A blocked request never reaches Dripify. To disconnect, remove the connection in Settings > Apps > Dripify, then revoke the key in Dripify under Settings > Integrations > API Key > Revoke.

FAQ

Generate a new key in Dripify under Settings > Integrations, then paste it into Settings > Apps > Dripify. Agents pick up the new key automatically.
Store it in Buckle. 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.
Yes. Connect each account’s key separately and tell them apart with the Connection label under Advanced.
Yes. Set message sending to need approval when you grant the connection.