Zapier

Pingram is in the Zapier App Directory (public beta). Add it as an action in a Zap to send email or SMS when something happens in another app.

There are no Pingram triggers. Use another app (Gmail, HubSpot, Stripe, a catch hook, and so on) as the trigger, then Pingram as the action.

Connect

  1. Open API Keys in your Pingram dashboard: US, Canada, or EU.
  2. Copy the secret key that starts with pingram_sk_.
  3. In Zapier, add a Pingram action and create a new connection.
  4. Paste the API key and pick the same Region shown on that API Keys screen (us, ca, or eu).

The connection label is the region, so US vs Canada vs EU accounts stay distinct if you connect more than one.

Send Email

Field Required Description
To yes Recipient email
Subject yes Subject line
HTML Body yes HTML for the email. Write it in this Zap step.
Type no Label stored on the Pingram log. Defaults to zapier.
From Name no Sender display name
From Address no Must be on a verified domain. Leave blank for the built-in sender.
Preview Text no Inbox preview text

Map fields from the trigger into To, Subject, and HTML Body. The HTML is the email — Pingram does not pull a dashboard template in this step.

Send SMS

Field Required Description
To yes Phone number in E.164 format, such as +15551234567
Message yes SMS body
Type no Label stored on the Pingram log. Defaults to zapier.
From no A dedicated Pingram number on this account. Leave blank to use the default sender.

US SMS uses Pingram’s A2P 10DLC registration. See SMS senders and A2P 10DLC if you need a dedicated number or brand registration.

After you send

Each action returns a trackingId. Open Logs in the Pingram dashboard to see delivery for that send. Failed Zaps also show the API error in Zap history.

Type is how sends are grouped in Logs and Insights. Use a stable name per workflow (order_shipped, form_confirm) if you want those Zaps to show up as their own rows instead of the default zapier type.