Bupple
Automate with Bupple

Automate with Bupple

When a post goes live

Each time a post is published, a webhook tells your CRM, your sheet or your team's channel — with the caption, the accounts and the post's links.

Bupple is at the start: a post goes out, and the rest of the business hears about it. The campaign's company in HubSpot gets a note, a reporting sheet gets a row, the account team's channel gets the link.

The recipe, in any tool

Make the receiving step in your tool and copy its URL.

Add a webhook in Settings › Webhooks with that URL. Scope it to a brand or one campaign if you like, and under Posts pick Post publish render completed — a post Bupple published (scheduler.post.publish.render.completed.v1); add Post publish render failed too if your team should hear about a post that did not go out. Each event's Example shows exactly what it carries. (Post external publish completed is a post made outside Bupple; its call carries the account it was posted from, not the post.)

Map the fields in the next step: the post's caption, its networks and accounts with their handles, its times and its links are in the call's data.post.

In your tools

HubSpot's When a webhook is received trigger only enrolls a record that already exists, matched on a property — so either send the webhook to Zapier, n8n or Make and create the note there with HubSpot's step, or keep a property that matches what the call carries (the campaign's name, for example).

Zapier, n8n or Make: the webhook trigger → Google Sheets › Add a row with the post's date, networks, caption and link.

The webhook trigger → a message to the channel with the post's link. To have Bupple tell a Slack channel without another tool, an automation's Send the result can post there directly.

  • Webhooks — every event, and how to check a call came from Bupple.
  • Posts — how posts are made and scheduled in Bupple.