AGENT SKILL

pm-sendpulse

SendPulse connector knowledge and safe action guide.

License 许可
AGPL-3.0
所属仓库
polymetrics-ai/cli
最近更新
2026-09-21
Stars
★ 7
Forks
0

01 前言 Front Matter

name
pm-sendpulse
description
SendPulse connector knowledge and safe action guide.

02 资源文件 1

03 SKILL.md 正文

pm-sendpulse

Purpose

Reads SendPulse address books, campaigns, senders, per-book emails, and the account blacklist, and writes address-book/sender/blacklist lifecycle mutations and campaign create/cancel actions through the SendPulse API.

Icon

Capabilities

  • check=true catalog=true read=true write=true query=false
  • Integration type: api

Authentication

  • Use pm credentials add with --from-env or --value-stdin for secret fields.

Configuration

  • base_url
  • token_url
  • client_id (secret) (required)
  • client_secret (secret) (required)

ETL Streams

  • addressbooks:
    • primary key: id
    • fields: all_email_qty(integer), id(integer), name(string)
  • campaigns:
    • primary key: id
    • fields: id(integer), name(string), status(string)
  • senders:
    • primary key: email
    • fields: email(string), name(string)
  • blacklist:
    • primary key: email
    • fields: comment(string), email(string)
  • emails_in_book:
    • primary key: email
    • fields: book_id(string), email(string), status(integer)

Sync Modes

  • ETL sync modes: full_refresh_append, full_refresh_overwrite

Reverse ETL Actions

  • create_addressbook:
    • endpoint: POST /addressbooks
    • required fields: bookName
    • risk: creates a new address book (mailing list); external mutation, approval required
  • update_addressbook:
    • endpoint: PUT /addressbooks/{{ record.id }}
    • required fields: id, name
    • risk: renames an existing address book
  • delete_addressbook:
    • endpoint: DELETE /addressbooks/{{ record.id }}
    • required fields: id
    • risk: permanently removes an address book and all its subscriber associations; irreversible
  • add_emails_to_book:
    • endpoint: POST /addressbooks/{{ record.id }}/emails
    • required fields: id, emails
    • risk: subscribes new email addresses to an address book; each add may trigger a double opt-in confirmation email depending on account settings
  • remove_emails_from_book:
    • endpoint: DELETE /addressbooks/{{ record.id }}/emails
    • required fields: id, emails
    • risk: unsubscribes the given email addresses from an address book; irreversible without re-adding them
  • create_campaign:
    • endpoint: POST /campaigns
    • required fields: sender_name, sender_email, subject, body, list_id
    • risk: creates a new email campaign against a real address book; depending on account settings this may schedule actual sending to real subscribers, the highest-impact action in this bundle, approval required
  • cancel_campaign:
    • endpoint: DELETE /campaigns/{{ record.id }}
    • required fields: id
    • risk: cancels a scheduled/in-progress campaign; stops further sends but does not un-send already-delivered emails
  • add_sender:
    • endpoint: POST /senders
    • required fields: email, name
    • risk: registers a new sender email address, which SendPulse will send an activation email to; low-risk external mutation
  • remove_sender:
    • endpoint: DELETE /senders
    • required fields: email
    • risk: removes a sender email address; any campaign still referencing it as its sender will fail to send
  • add_to_blacklist:
    • endpoint: POST /blacklist
    • required fields: emails
    • risk: permanently suppresses future sends to the given address(es) account-wide
  • remove_from_blacklist:
    • endpoint: DELETE /blacklist
    • required fields: emails
    • risk: removes an address from the account-wide suppression list; future campaigns can reach it again

Security

  • read risk: external SendPulse API read of address book, campaign, sender, per-book-email, and blacklist data
  • write risk: external SendPulse API mutation, including creating email campaigns that may send to real subscribers
  • approval: reverse ETL plan approval required before writes
  • Never pass secret values in chat, shell arguments, logs, docs, or JSON output.

Commands

Inspect as a manual

pm connectors inspect sendpulse

Inspect as structured JSON

pm connectors inspect sendpulse --json

Agent Rules

  • Run pm connectors inspect sendpulse before creating credentials or plans.
  • Use --json only when the caller needs structured output; use the manual for human-readable guidance.
  • Never ask the user to paste secret values into chat.
  • For reverse ETL writes, create a plan, show the preview, wait for explicit approval, then run with the approval token.

04 同仓库更多 Skills