Automate with Bupple
A welcome note for a new lead
A new lead in your CRM or a form starts an automation through its start link; Bupple writes a welcome note in your brand's voice, and your team gets it in Slack or by email.
A form is filled in or a contact lands in the CRM. A minute later the salesperson has a short, on-brand welcome note for that person, ready to send. Nothing goes out by itself: Bupple drafts, your team sends.
The recipe, in any tool
Plan the automation. In Automations: write a friendly two-sentence welcome note for the lead, using their first name, company and what they asked about. Open Schedule, switch on When another tool calls this link, set a small Credit limit, save and switch it on.
Choose where the note goes under Send the result: A Slack channel for the sales channel, A teammate's email for the lead's owner, or A webhook back into your CRM.
Call the start link from your CRM or form tool each time a lead arrives, with the fields as JSON (or as the form itself) and the lead's id as Idempotency-Key.
A real run on this recipe, started with {"first_name":"Sam","company":"Northwind","asked_about":"a demo"} sent as a form, took under two minutes and left the draft "Hi Sam, welcome to Bupple—we're thrilled to connect with you and the team at Northwind! …" — for 7 credits on the platform's model. Your price depends on the model and the length you ask for; the run's page says what each run spent.
In your tools
A contact-based workflow enrolls new leads → Send a webhook, method POST, the start link as the URL, Customize request body with first name, company, the question field and the record id. Send the note back with A webhook to a workflow that starts on When a webhook is received and writes it to a contact property or a task.
Trigger: New contact in your CRM, or New form entry. Action: Webhooks by Zapier › POST to the start link, payload type JSON, the fields as data.
Your trigger node → HTTP Request node: method POST, the start link as URL, Send Body as JSON with the fields, and an Idempotency-Key header from the lead's id.
Your trigger module → HTTP › Make a request: method POST, the start link, body type JSON (or Application/x-www-form-urlencoded), and the Idempotency-Key header.
Any form tool that can post its answers to a URL can use the start link as that URL — the fields become the run's data. From code it is one POST; see Start links.
Personalised video per lead
From a lead list to an email with a video made for each lead — Clay, HubSpot or HeyReach in, Bupple's Video Editor in the middle, a public link out to your email tool.
Finished video to your tools
When the Video Editor or the Design Editor finishes, a webhook hands the files to Zapier, n8n or Make — to save them to Google Drive, tell a channel, or start the next step.