Automate with Bupple
Bupple at the start
Let something that happens in Bupple — a finished video, a published post, a new DM, an automation's result — start a workflow in your other tools.
Bupple is at the start of a workflow when something that happens in Bupple is what sets your other tools going. A video is finished and your team's Slack hears about it. A post goes live and your CRM logs it. An automation writes a welcome note and your email tool sends it.
There are two ways to do it. Both POST a signed JSON message to a URL you give, and both retry by themselves when your tool does not answer.
1. A webhook for your whole workspace
In Settings › Webhooks you add a URL and pick the events it gets — every event, or only some, from the whole workspace, one brand or one campaign. From then on Bupple calls your URL each time one of them happens. Every call carries a copy of what it is about: the file with a download link, the post with its caption and links, the run with its drafts.
Use this when your tool decides what to do with an event. See Webhooks for the events you can pick and what each call carries.
2. An automation that sends its result
An automation can end by sending what it made to a webhook, a public link, a Slack channel or a teammate's email. You add these places on the automation's page, under Send the result. After every real run that finishes well, each place gets the files, their links and the run's data.
Use this when Bupple does the work on a schedule or on a moment — every Monday, write three LinkedIn posts from the week's news — and your tool takes it from there. See Sending results out.
Which one to use
| You want… | Use |
|---|---|
| To hear about everything that happens in a brand — files, posts, comments, DMs, runs | A workspace webhook |
| One automation's finished work, in one message, the moment it is done | Send the result on that automation |
| A link anyone can open to what an automation made | Send the result › A public link |
| Your team told in a channel | Send the result › A Slack channel |
Examples
- A finished video goes to the team's shared drive. A webhook on Video Editor and Design Editor events → your Zapier, n8n or Make flow downloads the file from the link in the call and saves it where you keep finished videos. See Finished video to your tools.
- A published post is logged in your CRM. A webhook on the post events → a HubSpot note on the campaign's company. See When a post goes live.
Automate with Bupple
Put Bupple at the start, in the middle or at the end of the workflows your team already runs — in Zapier, n8n, Make, Clay, HubSpot or your own code.
Bupple in the middle
Another tool hands Bupple data, Bupple makes something with it, and the result goes on to the next step — the start link or the API in, the result out.