View as Markdown
Reply.io icon

Reply.io TRIGGER

New Link Clicked

Emit new event when a link is clicked in a campaign. See the docs here
  • Trigger
  • Polling
  • 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.

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 Link Clicked configuration
Property Type Description
timer Timer $.interface.timer
The timer that will trigger the event source
Required
campaignId Campaign string
The campaign identifier
Required Dynamic
stepId Step string
The step identifier
Required Dynamic

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 — after each poll.

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-link-clicked
Version
0.0.1
App
Reply.io
Authentication
API key
Delivery
Polling source
Output
Events emitted by Reply.io.