View as Markdown
Emailoctopus icon

Emailoctopus TRIGGER

New List Contact

Emit new event each time a contact is added to a list.
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Emailoctopus 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: "emailoctopus-new-list-contact",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    emailoctopus: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    listId: "List",
  },
  webhookUrl: "https://example.com/webhooks/emailoctopus",
})

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 List Contact configuration
Property Type Description
timer Timer $.interface.timer
Required
listId List string
List where the source will be performed.
Required Dynamic

01

Connect

Your user authorizes Emailoctopus 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
emailoctopus-new-list-contact
Version
0.0.4
App
Emailoctopus
Authentication
API key
Delivery
Polling source
Output
Events emitted by Emailoctopus.