Pingram Roundup - September 2026

September shipped email broadcasts, auto upgrade when you hit your budget, and a stack of agent integrations. Here is what is announce-worthy; the rest stays on the changelog.

Email

Create, schedule, and send email campaigns from the dashboard or the Broadcasts API. Target identified users with property filters, or send to a raw email list. Personalize subject and HTML with Liquid mergetags, and track delivery and engagement. Full walkthrough in announcing broadcasts.

user.identify now accepts a properties map for custom attributes (first name, plan, and so on). Use those attributes in broadcast audience filters and in templates as {{ user.properties.firstname }}. Later identify calls merge new keys; omitted keys stay unchanged.

On send, set options.email.openTracking or options.email.clickTracking to false to skip that tracking for one email. openTracking: false adds no open pixel; clickTracking: false leaves links as written. Same fields on POST /email, including scheduled sends. Delivery, bounce, and complaint events still record. Details in email tracking controls.

await pingram.send({
  type: 'order_update',
  to: { id: 'user_123', email: 'user@example.com' },
  options: {
    email: {
      openTracking: false,
      clickTracking: false
    }
  }
});

Plans and billing

Paid accounts can turn on Auto upgrade in Settings → Plan. When spend reaches 90% of the monthly budget, we move you up one tier and charge the difference. GET /account includes autoUpgrade; PATCH /account with { "autoUpgrade": true } turns it on. See announcing auto upgrade.

Changing your paid plan in Settings no longer sends you through checkout again. Upgrades apply immediately; downgrades take effect at the end of the current billing period. The Plan page shows the scheduled plan and when it starts.

Multi-factor authentication is included on every paid plan, not only Enterprise. Enable an authenticator app from Profile → Security.

Integrations

Settings → Integrations lists official Pingram integrations in one place (n8n, Make, Apprise, GitHub Actions, MCP, Hermes, Skills, the CLI, Auth0, and more). Copy the MCP server URL or an install command from a card, then open the setup guide.

Connect OpenClaw (ClawBot) to Pingram’s hosted MCP so your agent can send email and SMS, check delivery logs, and manage your account after one OAuth login. Setup guide and optional ClawHub skill: OpenClaw integration.

Send email and SMS from Make scenarios with the verified Pingram app, including a custom API call for other Pingram requests. Setup and example scenarios: Make integration. Announcement: Pingram on Make.

Install the Pingram plugin in Cursor to send email and SMS and manage your account from the editor. One install connects the hosted MCP server and Pingram skills; sign in once with your Pingram account. The same plugin works in Grok Bot. Canada and EU accounts should use their regional MCP host. Details in the Cursor plugin announcement.

Agent tooling

After you connect Pingram MCP, pass an optional accountId from List Accounts to send messages, list numbers, or manage 10DLC on that account. Without accountId, tools still use your first account. Reconnect the connector (or refresh tools) so clients pick up the new argument.

AI agents can list, create, update, and delete webhook endpoints through the Pingram MCP connector. The Pingram CLI webhooks commands cover the same operations.

The Pingram MCP connector publishes OpenID Connect UserInfo, so ChatGPT Enterprise can restrict who links Pingram by verified email domain.

Full ship list: changelog.