Automation destinations

Each destination shapes the report to suit where it lands. A Slack message is not a Word document, and a CRM note is not a checklist. This is what to expect from each one.

Messaging

Slack: Posts the report as a message. Pick one or more channels, or send it directly to people. Klang must be in the channel; for a private channel, invite it first.

Microsoft Teams: Posts a card in a channel or chat. Long reports collapse behind Show details so the channel stays readable. The first time you use it, Klang installs its app into your Teams tenant.

Both can send ToDos as a checklist.

Documents and pages

Notion: Creates a page under a page or database you choose. ToDos become real Notion checkboxes.

Google Drive: Creates a Google Doc with real headings, in the folder you pick.

OneDrive: Creates a Word document in the folder you pick.

Dropbox: Saves a PDF in the folder you pick.

The file destinations write a document, so they do not offer the ToDo-only option. A bare task list is not a document anyone wants to open.

CRM

HubSpot and Pipedrive match the meeting’s external participants to people in your CRM by email address, then write the report as a note on them and on their open deals. They can also fill in fields you choose: Klang reads the meeting and proposes a value for each one.

A few things worth knowing before you point one at a customer’s records:

• Add the Only external meetings condition. Without it, your internal standups end up on customer records.
• Choose deliberately whether Klang may create records that don’t exist yet. Pipedrive has separate switches for creating a person and creating a lead.
• When Klang cannot tell which record a meeting belongs to, the run waits for you instead of guessing. It appears in the history asking you to pick, and you get an email.
• Test first. For these two, Test on an earlier meeting is a preview: it shows what it would write without writing it.

Email

Email sends the report as a mail. Send it to addresses you type in, or to the meeting’s own participants. Participant sending only works for meetings that came from a calendar invitation, since that is where the addresses come from.

Your own system

Webhook: Sends the report to a web address you control, as a signed JSON request. Use it to push meeting data straight into your own database or app, or into a tool like Zapier, Make, or n8n.

By default Klang sends everything it has: the meeting, the report, and the full analysis. If your system expects its own field names, add fields and choose what each one contains: the summary, the ToDo list, the participants’ email addresses, or a fixed value you type in.

You add the address in the automation itself. Enter it, click Add, and copy the signing secret Klang shows. Your server uses the secret to check that the request really came from Klang. You can find it again later under Webhooks.

Addresses are reusable. Once added, the same one is available to every automation, and it appears under Webhooks where you can see each delivery and what your server replied.

Connecting a destination

The first time you choose a destination that needs a connection, Klang shows Connect. That opens the provider’s own login in a new window; approve the access and the window closes on its own. You only do this once per service.

A connection can stop working later, when someone revokes access, an admin removes the app, or a password changes. When that happens Klang pauses the automation, tells you by email, and shows Connect again on its page. Meetings that happened while it was paused are not sent afterwards; run them from the history when the connection is fixed.