View as Markdown
Patreon icon

Patreon TRIGGER

Member Deleted

Emit new event for each deleted member
  • Trigger
  • Instant
  • OAuth
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Patreon 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: "patreon-member-deleted",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    patreon: { authProvisionId: "apn_xxxxxxx" },
    campaign: "Campaign",
  },
  webhookUrl: "https://example.com/webhooks/patreon",
})

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.

Member Deleted configuration
Property Type Description
campaign Campaign string
Patreon Campaign
Required Dynamic

01

Connect

Your user authorizes Patreon 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
patreon-member-deleted
Version
0.0.1
App
Patreon
Authentication
OAuth
Delivery
Instant event
Output
Events emitted by Patreon.