View as Markdown
Reply.io icon

Reply.io TRIGGER

New Prospect Finished (Instant)

Emit new event when a prospect finishes the sequence. See the docs here
  • Trigger
  • Instant
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Reply.io account, configure the source, and choose the webhook where your backend receives events.

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 deployed = await pd.triggers.deploy({
  id: "reply_io-new-prospect-finished",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    reply_io: { authProvisionId: "apn_xxxxxxx" },
    finishReasons: ["Finish Reasons"],
  },
  webhookUrl: "https://example.com/webhooks/reply-io",
})

console.log(deployed.id)

MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.

SCHEMA

Configuration

These inputs define which events the source watches. Dynamic options are loaded from the connected account.

New Prospect Finished (Instant) configuration
Property Type Description
finishReasons Finish Reasons string[]
The reason the sequence finished. Leave blank to include all reasons
Optional

01

Connect

Your user authorizes Reply.io through Pipedream managed auth.

02

Deploy

Your backend deploys this source with that user's own configuration.

03

Webhook delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source — as it happens.

OR

On-demand retrieval

No webhook required. Your app or agent can fetch recent events from the trigger events API.

Registry key
reply_io-new-prospect-finished
Version
0.0.1
App
Reply.io
Authentication
API key
Delivery
Instant event
Output
Events emitted by Reply.io.