Bupple College
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.
Your team already has workflows: a lead lands in the CRM, a form is filled in, a campaign starts, an email goes out. Bupple can be one step of any of them. Something outside can start Bupple's work, and Bupple can hand the result to whatever comes next.
There are only two doors, and everything on these pages is one of them, or both:
- In — another tool starts Bupple's work. It calls the Bupple API with a key, or it calls an automation's start link with its data.
- Out — Bupple hands what it made to another tool. An automation sends its result to a webhook, a public link, a Slack channel or a teammate's email, and every event in your workspace can reach your URL as a webhook.
Any tool works
The recipes name Zapier, n8n, Make, Clay, HubSpot, Klaviyo, MailerSend and HeyReach because teams ask about them. None of them is special. Any tool that can send an HTTPS request, or receive one, can do everything on these pages — and so can a few lines of your own code.
Where Bupple sits in a workflow
| Bupple is… | What happens | Read |
|---|---|---|
| At the start | Something happens in Bupple — a video is finished, a post goes live, a DM arrives — and your other tools act on it. | Bupple at the start |
| In the middle | Another tool hands Bupple data, Bupple makes something with it, and hands the result to the next step. | Bupple in the middle |
| At the end | Your workflow's last step asks Bupple to make, save or schedule something, and it lands in Bupple for your team. | Bupple at the end |
Before you start
- The Bupple API and start links are switched on per workspace. When they are on, Account settings › Bupple API is in the menu and an automation offers When another tool calls this link. If you do not see them, ask Bupple to switch them on for your workspace.
- Everything still follows your team's rules. A key or a start link works as the person who made it, only in the workspaces and brands it was given, and only with the permissions that person has.
- Anything that costs credits says its price first. Over the API a paid call answers its price and spends nothing until the call says
"confirm": true. An automation spends at most its own credit limit per run. - An automation only drafts. A run started from outside follows the same rule as any other run: it makes drafts and files, and never publishes, sends or deletes by itself. Sending its result out is a step you choose on its page.
What to read next
- API keys — make a key and keep it safe.
- Personalised video per lead — the whole road from a lead list to an email with a video link.