Create Kleer Client
Creates a new client in Kleer from the enrolled company in a HubSpot workflow.
Workflow Type
Company-based — This action is available in company workflows.
Variants
| Action | Description |
|---|---|
| Create Kleer Client | You configure each field manually with static values or data tokens |
| Create Kleer Client (from mappings) | Uses your configured client field mappings automatically — no input fields needed |
Input Fields (Standard Variant)
All fields are optional. If not provided, the client will be created with Kleer's defaults.
| Field | Type | Description |
|---|---|---|
| Client Name | Text | Name of the client in Kleer |
| Organization Number | Text | Organization number (e.g. 556677-8899) |
| VAT Number | Text | VAT registration number (e.g. SE556677889901) |
| Client Type | Text | Type of client — see values below |
| Foreign ID | Text | External reference ID |
| Payment Days | Number | Number of days until payment is due |
| Delivery Type | Text | How invoices are delivered — see values below |
| Text | Client email address (used for email delivery) | |
| Address Line 1 | Text | Street address line 1 |
| Address Line 2 | Text | Street address line 2 |
| Zip Code | Text | Postal code |
| State | Text | State or region |
| Country | Text | Country name |
Accepted Values
Client Type
Organisation, Person
Delivery Type
Mail, Email, Manually, Svefaktura
Behavior
- The action reads the enrolled company from HubSpot
- A new client is created in Kleer with the provided field values
- The new Kleer client ID is written back to the
kleer_idproperty on the HubSpot company - If
kleer_idis already set on the company, the action is skipped (idempotent)
Tips
- Use HubSpot data tokens to pull values dynamically from the enrolled company's properties (e.g. map Company Name to Client Name)
- The "from mappings" variant is useful if you've already configured detailed client field mappings and want the same mapping logic applied during creation