Klang matches the people in the meeting to your HubSpot contacts and writes the meeting up where your pipeline already lives, so the CRM stays current without anyone doing admin.
An automation sends the report from a finished meeting somewhere else, without anyone clicking anything. You pick three things: where it goes, what it sends, and which meetings it runs on.
In Settings, Integrations, add HubSpot, sign in and approve the access it asks for.
Do this before anything else. It stops internal meetings appearing on customer records, which is the mistake worth avoiding here.
Klang reads the meeting and proposes a value for each property you pick, so the structured parts of your pipeline fill themselves in.
Run the automation against a past meeting and check what it would have written. CRM records are seen by colleagues and are worth getting right first time.
Without conditions an automation runs on all your new meetings. Pick whether all of your conditions have to be true, or any one of them.
A folder and its subfolders.
A tag someone has applied. A suggested tag does not count.
Your text anywhere in the title.
One person, by email or name.
Anyone from a given organisation.
At least one participant from outside. Reach for this before writing to a CRM.
Conditions look at the meeting, not at what was said in it. There is no condition for “meetings where we discussed pricing”, so put that kind of judgement in the instructions instead.
Record your next meeting in Klang and let the write-up find its way to HubSpot on its own.