
Tell another tool when a student finishes a lesson, a course or joins my list
Your course lives in bernard, but you might still use another tool for some things: ActiveCampaign while you move, a spreadsheet of who finished, a community app that needs to know who has joined. A webhook is how bernard tells that tool, straight away, when something happens.
The prompt
“Connect [my site] to [Zapier / Make / my own system] so it hears when [a student finishes a course / someone new joins my contacts / a tag is added / someone fills in my contact form / my content calendar changes]. Tell me exactly what personal data will be sent before you switch it on.”
Signed in, Get my prompt fills in your site for you. Otherwise press Copy and fill in the [bracketed] parts. First time? Connect your AI to bernard once: Use your own AI (opens in a new tab).
What bernard can tell it
You choose which of these each connection hears about:
- a student joins a course;
- a student finishes a lesson or finishes a module;
- a student passes a quiz, or passes every required quiz;
- a student finishes a course, or gets their certificate;
- a new person arrives in your contacts from a sale, an enrolment or a form on your site (not people you import or add by hand);
- a person is given a tag;
- someone fills in a form on your site (an enquiry, a sign-up, a registration), including a test you send yourself from a draft page;
- something is added to your content calendar, moves to another day (or back to the shelf), or is marked done, skipped or planned again.
When Bernard plans your calendar or suggests a set of posts, each new item is its own message. In a tool like Zapier that can be a few dozen tasks at once, so choose the calendar messages only for a tool that needs them, such as a team board. If your team keeps its board in Notion and uses Sasha, see Get my website enquiries and content plan onto our Notion board.
A video or audio lesson counts as finished when it plays to the end or most of it has played, a text lesson when the student reaches the end of it, and a quiz lesson when the student passes the quiz. These are the same moments your course emails use (Email my students when they reach each point in my course).
Exactly what leaves bernard
A message about a person carries their email address and name. A course message also says which course, and which lesson, module, quiz or certificate. A tag message says which tag. A form message carries every answer they typed, which form it was, and a link to the person in bernard; if the form has a field called “company” or “message”, those answers are also sent on their own, so the other tool can find them easily. When the person came from a link with campaign tags, a form message also carries that campaign (for example the source, medium and campaign name), the page they landed on and the website that sent them. Nothing else: no payment details, and no answers from any other form.
A content calendar message carries no personal data: only the item’s title, its day, its type, whether it is planned, done or skipped, and a link to it in your calendar.
That is still personal data going to another company, so only the account owner can switch a connection on. Bernard shows you the sentence first, for example “bernard will send the email address, name and course progress of your students to hooks.zapier.com”, and nothing is connected until you approve it.
The messages always have the same shape, so the other tool keeps working. Bernard cannot invent a new one.
Setting one up
Ask Bernard in the Workshop, for example “tell Zapier when a student finishes a
course”. It will ask for the address the other tool gave you (it must start
https://), show you what will be sent, and wait for your yes.
Then:
- If the other tool can check a signature, open Contacts, then Connect another tool (Bernard gives you the link). Next to the connection, press Show signing secret, then Copy, and paste it into the other tool. Only you see the secret; Bernard never does. Zapier’s “Catch Hook” step does not check signatures, so for a plain Zap you can skip this.
- Ask Bernard to send a test. It sends a made-up sample student, never a real one, and tells you what the other tool answered. For a form message, ask for a test of each form you care about: each sample carries that form’s own field names, with made-up answers.
- In the other tool, map the fields of the test message to what you want it to do, for example a tag in ActiveCampaign.
For the technically minded: each message is a POST of JSON, signed with
HMAC-SHA256 over the timestamp, a full stop, and the exact body, in the
X-Bernard-Signature header, with the timestamp in X-Bernard-Timestamp.
Reject a message whose timestamp is more than a few minutes old.
Checking it is working
Ask Bernard how your connections are doing. For each one it shows the last 20 deliveries: delivered or failed, what the other tool answered, and when. It never shows what was sent.
If the other tool is down, bernard tries again a few times. If a connection keeps failing, many times in a row, bernard switches it off and puts a note in your activity log. Ask Bernard to switch it back on once the other tool is fixed.
To stop sending, ask Bernard to switch the connection off or delete it; both are shown to you first and wait for your approval. Your contacts themselves are in Where do the people who buy, join or ask end up?.
Questions people ask
- Which things can bernard tell another tool about?
- 13: a student joins a course, finishes a lesson, finishes a module, passes a quiz, passes every required quiz, finishes a course or gets their certificate; a new person arrives in your contacts; a person is given a tag; someone fills in a form on your site; something is added to your content calendar, moves to another day, or is marked done, skipped or planned again. You choose which ones each connection hears about.
- What personal data leaves bernard?
- For a person event, the person’s email address and name, every time. For a course event, also which course and which lesson, module, quiz or certificate. For a tag, the tag. For a form, everything they typed into it. A content calendar event carries no personal data at all, only the item’s title, day, type and state. Nothing else: no phone number unless they typed it into a form, no payment details. Before anything is switched on, Bernard shows you the exact sentence and the company it goes to, and waits for your approval.
- Who can set this up?
- Only the account owner, because it sends your contacts’ details to another company. A team member who asks is told so.
- What is the secret for?
- Every message bernard sends carries a signature made with a secret, so the other tool can check it really came from bernard. Only the account owner sees the secret: in Contacts, under Connect another tool, press Show signing secret next to the connection, then Copy. Bernard never sees it, so it sends you there rather than paste it into the chat. You can copy it again at any time.
- What happens if the other tool is down?
- bernard tries again five more times over about half an hour, and you can see what happened to each of the last 20 deliveries. If a connection fails many times in a row, bernard switches it off and says so in your activity log, so a dead address stops piling up.
- Can I try it without sending a real person’s details?
- Yes. Ask Bernard to send a test. It sends made-up data, a sample person at an example address (or a sample calendar item), and tells you what the other tool answered. To test a form, ask for a test of that form: the sample uses your form’s own field names, with made-up answers. This works for forms that save to your bernard contacts, because only those send a message.
- Will students who finished lessons before I connected it be sent?
- No. Only things that happen after the connection is made are sent. A student’s older lessons that their browser reports later are not sent either.