View as Markdown
Woodpecker.co icon

Woodpecker.co ACTION

Stop Follow-Ups

This action updates a prospect to stop receiving follow-ups. See the docs here
  • Action
  • Writes data
  • Destructive
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Woodpecker.co account once, then configure and run Stop Follow-Ups from your backend or agent.

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: "woodpecker_co-stop-follow-ups",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    woodpecker_co: { authProvisionId: "apn_xxxxxxx" },
    campaignId: 10,
    id: 10,
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Stop Follow-Ups inputs
Property Type Description
campaignId Campaign integer
Campaign ID.
Required Dynamic
id Id integer
Prospect's ID.
Required Dynamic

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
woodpecker_co-stop-follow-ups
Version
0.0.2
App
Woodpecker.co
Authentication
API key
Read-only
No
Destructive
Yes
Open world
Yes