CONNECT APP
Build with Reply.io
Marketing
- API key
MCP
Give your agent Reply.io tools
Every Reply.io action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Reply.io account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "reply_io",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create or Update Contact:
const result = await mcp.callTool({
name: "reply_io-create-or-update-contact",
arguments: {
email: "Email",
firstName: "First Name",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "reply_io",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create or Update Contact:
result = await session.call_tool("reply_io-create-or-update-contact", {
"email": "Email",
"firstName": "First Name",
})API PROXY
Call the Reply.io API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Reply.io API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.reply.io/v1/people",
})
// Any allowed Reply.io endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.reply.io/v1/people
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkucmVwbHkuaW8vdjEvcGVvcGxl?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Reply.io actions from your backend
Connect a user's Reply.io account once, then run Create or Update Contact on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "reply_io-create-or-update-contact",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
reply_io: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
firstName: "First Name",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="reply_io-create-or-update-contact",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"reply_io": {"authProvisionId": "apn_xxxxxxx"},
"email": "Email",
"firstName": "First Name",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "reply_io-create-or-update-contact",
"configured_props": {
"reply_io": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email",
"firstName": "First Name"
}
}'TOOLS
Reply.io actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create or Update Contact
actionCreate a new contact or update if they already exist. See the docs hereWritev0.0.2 -
Create or Update Contact and Push to Campaign
actionCreate a new contact, or update if they already exist, and push contact to the selected campaign. See the docs hereWritev0.0.2 -
List Campaign ID Options
actionRetrieves available options for the Campaign ID field.Read-onlyv0.0.1 -
Mark Contact as Finished
actionMark a contact as finished in all campaigns by their email address. See the docs hereWritev0.0.2 -
Mark Contact as Replied
actionMark a contact as replied in all campaigns by their email address. See the docs hereWritev0.0.2 -
Remove Contact From Campaign
actionRemove an existing contact from the selected campaign. See the docs hereWritev0.0.2
EVENTS
Reply.io triggers
Event sources your backend can deploy for users and receive through a webhook.
-
New Contact Added
triggerEmit new event when a new contact is added. See the docs herev0.0.1 -
New Contact Opted Out (Instant)
triggerEmit new event when a person opts out. See the docs hereInstantv0.0.1 -
New Email Opened (Instant)
triggerEmit new event when a person opens your email. See the docs hereInstantv0.0.1 -
New Email Replied (Instant)
triggerEmit new event when a prospect replies to an email. See the docs hereInstantv0.0.1 -
New Email Sent (Instant)
triggerEmit new event when a new email is sent (first step or follow-up). See the docs hereInstantv0.0.1 -
New Link Clicked
triggerEmit new event when a link is clicked in a campaign. See the docs herev0.0.1 -
New Prospect Finished (Instant)
triggerEmit new event when a prospect finishes the sequence. See the docs hereInstantv0.0.1 -
New Reply Categorized (Instant)
triggerEmit new event when a reply is marked with a new inbox category. If an uncategorized category is assigned, the webhook will not be triggered. See the docs hereInstantv0.0.1
- App slug
- reply_io
- Authentication
- API key
- Categories
- Marketing
- Actions
- 6
- Triggers
- 8
- API proxy
- Available