Zapier Integration

Connect VoxBurst to thousands of apps — Google Sheets, Notion, Airtable, Slack, RSS feeds, and more — without writing a single line of code. Use Zapier to trigger posts automatically or send VoxBurst events to your other tools.

What you can do

Common use cases:

• Publish to social media when you add a row to a Google Sheet or Airtable base
• Post content from an RSS feed automatically when new items appear
• Create a draft post in VoxBurst from a Notion database entry
• Send a Slack message to your team when a post fails to publish
• Log every published post to a Google Sheet for reporting

Prerequisites

• A VoxBurst account on the Solo plan or higher (API access required)
• A Zapier account  (free or paid)
• At least one social media account connected in VoxBurst
• A VoxBurst API key (posts:write scope)

Step 1: Get your VoxBurst API key

sk_live_xxxxxxxxxxxxx

Step 2: Find your account IDs

Every post in VoxBurst must specify which connected accounts to publish from. You’ll need the account ID(s) when setting up your Zap action.

curl https://api.voxburst.io/v1/accounts \
  -H "Authorization: Bearer sk_live_xxxxxxxxxxxxx"

{
  "data": [
    {
      "id": "acc_01hwxyz",
      "platform": "TWITTER",
      "name": "@yourusername",
      "connected": true
    },
    {
      "id": "acc_01habc",
      "platform": "LINKEDIN",
      "name": "Your Name",
      "connected": true
    }
  ]
}

Keep these IDs handy — you’ll paste them into the Zapier action fields.

Step 3: Create your Zap

Action: Create a post in VoxBurst

The VoxBurst app in Zapier includes a Create Post action. This is what sends content into VoxBurst.

Step 4: Set up a VoxBurst trigger (optional)

To send VoxBurst events to Zapier (e.g. when a post is published), use Webhooks by Zapier alongside VoxBurst’s webhook system.

Example Zaps

Google Sheets → schedule a post

Trigger: New row in Google Sheets Action: VoxBurst — Create Post

Map sheet columns to post fields:

• Row Message → Content
• Row Platforms → Platforms
• Row Account IDs → Account IDs
• Row Publish At → Scheduled For

Every new row you add to the sheet creates a scheduled post in VoxBurst.

RSS feed → publish immediately

Trigger: RSS by Zapier — New item in feed Action: VoxBurst — Create Post

Map RSS fields:

• {{Title}}: {{Link}} → Content
• TWITTER, LINKEDIN → Platforms (hardcoded)
• Your account IDs → Account IDs

New articles are published to your connected accounts automatically.

VoxBurst publish failure → Slack alert

Trigger: Webhooks by Zapier — Catch Hook (subscribed to post.failed) Action: Slack — Send message to a channel

Map VoxBurst payload fields:

• {{post.content}} → message body
• {{post.platforms[0].platform}} → platform name
• {{post.platforms[0].error}} → error message

Your team gets a Slack notification any time a post fails.

Webhook payload structure

When VoxBurst sends an event to your Zapier webhook trigger, the payload looks like this:

{
  "event": "post.published",
  "workspaceId": "ws_01hwxyz",
  "post": {
    "id": "post_abc123",
    "content": "Hello from VoxBurst!",
    "status": "PUBLISHED",
    "scheduledFor": "2026-04-10T14:00:00Z",
    "createdAt": "2026-04-09T10:00:00Z",
    "platforms": [
      {
        "platform": "TWITTER",
        "accountId": "acc_01hwxyz",
        "accountName": "@yourusername",
        "status": "published",
        "platformPostId": "1234567890",
        "platformPostUrl": "https://x.com/yourusername/status/1234567890",
        "publishedAt": "2026-04-10T14:00:05Z",
        "error": null
      }
    ]
  }
}

For post.failed events, platforms[n].error will contain the failure reason.

Verifying webhook signatures

VoxBurst signs every outgoing webhook with an HMAC-SHA256 signature. The signature is sent in the X-VoxBurst-Signature header using a Stripe-style format:

X-VoxBurst-Signature: t=1234567890,v2=abc123def456...

Where:

• t is the Unix timestamp (seconds) when the webhook was sent
• v2 is the HMAC-SHA256 of ${t}.${rawBody} using your signing secret

To verify:

const crypto = require('crypto')
 
function verifySignature(rawBody, secret, signatureHeader) {
  const parts = Object.fromEntries(
    signatureHeader.split(',').map(p => p.split('=', 2))
  )
  const timestamp = parts['t']
  const receivedSig = parts['v2']
  if (!timestamp || !receivedSig) return false
 
  const expected = crypto
    .createHmac('sha256', secret)
    .update(`${timestamp}.${rawBody}`, 'utf8')
    .digest('hex')
  return crypto.timingSafeEqual(
    Buffer.from(expected, 'hex'),
    Buffer.from(receivedSig, 'hex')
  )
}

Troubleshooting

”Authentication failed” in Zapier

• Confirm the API key starts with sk_live_ (not sk_test_)
• Check the key has the posts:write scope enabled
• Keys can be regenerated in Settings → API Keys

Post created but not publishing

• Check that scheduledFor is in the future, in ISO 8601 format (e.g. 2026-04-10T14:00:00Z)
• Leave scheduledFor empty to publish immediately
• Confirm the account IDs are correct and the accounts are still connected

Zapier webhook trigger not receiving events

• Make sure the webhook URL in VoxBurst is the exact URL Zapier provided
• Check that you selected the correct event types when registering the endpoint
• Use Test on the webhook endpoint in Settings → Integrations to send a test payload
• Delivery history is available by clicking Log next to the endpoint

Posts show up in VoxBurst but don’t reach social platforms

• Check the account health in Accounts — look for any token errors
• Confirm the platform account is still connected and authorized
• Check the post’s platform status in the VoxBurst calendar for the specific error message

Limits

See Supported Platforms for per-platform content limits.

Need help?

• VoxBurst API Reference
• Webhook events reference
• Supported platforms
• Email support: support@voxburst.io