← All use cases
Intake & forms

Event registrations, captured automatically

Registration via Tally → entry in Baserow, confirmation email.

Registration via TallyTally
  • Add Baserow entryBaserow
  • Send confirmation emailEmail account

The Dialograum initiative runs every registration for its events through this konnektor. Here’s how it’s built and what each step does.

The konnektor at a glance

A konnektor is a process automation: aktors that run one after another. An aktor is the smallest step, such as a call to an API (say, adding a row to a table) or sending an email. The product page has more on both.

The konnektor on konnek's visual canvas. At the top, two triggers: "Manual input" and the Tally form. Below them, one after another, the steps baserow_createRow marked POST, Dialograum_Email_Aktor and Ausgabe-Mapping (output mapping).
Its triggers and steps: the konnektor behind the registrations.

Like every konnektor, this one can be started by hand, with real data or test data. Most of the time, though, it starts from a Tally form.

Save the registration in Baserow

baserow_createRow is an HTTP aktor. It’s already built, so you can drop it straight into a konnektor. So what does it actually do? It sends a POST request to the Baserow API, which adds a new row to the table. It needs four inputs:

  • base_url is the address of the Baserow API, here https://api.baserow.io.
  • table_id picks the table the registration goes into.
  • rows_input sets which answer from the form goes into which field of the table.
  • database_token is the access key for Baserow. It’s stored in konnek’s secrets, and the aktor only refers to it.
The inputs of the baserow_createRow aktor: base_url set to https://api.baserow.io, table_id, rows_input with five fields mapped to the form answers vorname, nachname, email, motivation and termin, and database_token pointing to a secret. The IDs are blurred.
Every field in the Baserow table gets an answer from the form. We blurred the IDs.

The API names each Baserow field field_ followed by a number. You don’t have to work out which answer belongs in which field. The agent does that for you:

  1. Once the Tally form is connected, konnek knows its fields.
  2. A separate aktor fetches all the fields of the Baserow table. You only say which table the data should go into.
  3. The agent compares the two lists and maps each answer to its field in Baserow. All you do at the end is confirm it.

Send the confirmation

An email aktor makes sending emails easy and flexible. The sender, subject and text are set in the step itself. The person’s name and email address come from the form.

Plain-text emails work fine. If you want your emails to match your brand, paste in HTML and send polished, professional messages. Here, everyone who registers gets a confirmation with a footer in Dialograum’s design: logo, website link, signature, and links to LinkedIn, the legal notice and the privacy policy.

The Dialograum_Email_Aktor email aktor of type send_mail. The sender is katrin@dialograum.org, the subject is the variable subject. The message body in HTML mode consists of the variable emailText and a footer with the Dialograum logo, a line about the initiative, the link dialograum.eu, a signature with the placeholders {{{name}}} and {{{AUFGABENBEREICH}}} and the address {{{name}}}@dialograum.org, and the links LinkedIn, Impressum and Datenschutz. Below it, the aktor's metadata with its version and last update; the ID is blurred.
The confirmation text, with the HTML footer below it that stays the same in every email.

Output mapping

You can always pass the information that matters on to the last step, the output mapping. Here, that could be the new row in the table and perhaps the time the email went out. The output mapping is optional, but it’s useful for your reporting or for processes that build on this one.

Tools in this flow

Swap any of them.

  • Tally Belgium
  • Baserow Netherlands

Your process not listed?

Happy to show you how konnek can automate your specific workflow.

Talk to us