Zapier enables you to link Kinnovis with over 2,000 other web services. With Zaps - automated workflows that can be set up in minutes without coding - you can streamline daily tasks and connect apps that wouldn’t normally integrate.
Each Zap begins with a Trigger, which is the app (Kinnovis) that provides the information and initiates the workflow. This then leads to one or more Actions in other apps, where the data is automatically sent and processed.
Getting Started
How do I connect Kinnovis to Zapier?
Contact Kinnovis support team via Intercom that you want to use Zapier.
You'll receive an invitation link to sign up or log in.
Once logged in, you'll gain access to our Kinnovis profile in Zapier.
Go to “Apps”, there you will see “Kinnovis Manager (1.0.0)”.
Since our Zapier account is currently private, this invitation-only Kinnovis app is required. However, rest assured that all functionalities remain fully available, even with a private profile.
Get your API Key
You will receive the Kinnovis API Key from our support team.
Then go to Zapier to connect and authorize your Kinnovis account.
Enter the API Key
Click on "Select".
2. Enter the AI key you received from our Kinnovis support team.
3. Once you have entered the key, your Kinnovis account is now connected to Zapier.
Once that’s complete, you can begin setting up an automation! Choose from a pre-made Zap or customise your own using the Zap Editor. No coding skills are needed, and the process will guide you through each step.
How to use Zaps
Key Components of a Zap:
Trigger: The event in one app that starts the workflow (e.g., "A new customer is added in Kinnovis").
Action: The task(s) performed in response to the trigger in another app (e.g., "Send a welcome email through Gmail").
Triggers
Triggers are events which are sent from a Kinnovis to Zapier or Zapier is pulling data.
Examples:
Trigger | Description |
New Customer | Triggers when there is a new customer created in the Manager or over the Booking Portal. |
New Lead | Triggers when there is a new customer with status LEAD created in the Manager or over the Booking Portal. |
New Booking | Triggers when there is a new booking created in the Manager or over the Booking Portal. |
New Invoice | Triggers when there is a new invoice created in the Manager. |
New Credit Note | Triggers when there is a new credit note created in the Manager. |
Booking Update | Triggers when there is a booking updated in the Manager. |
Customer Update | Triggers when there is a customer updated in the Manager. |
Invoice Update | Triggers when there is an invoice updated in the Manager. |
Credit Note Update | Triggers when there is a credit note updated in the Manager. |
We’ll extend this list on the go once we have more endpoints in the public API. The triggers some up what’s possible until now.
Actions
In Zapier, actions are the tasks or events that occur as a result of a trigger. Once a trigger initiates a Zap (Zapier's automation workflow), an action defines what happens next in the connected app(s). Actions are essentially the "do this" part of the "if this, then that" automation.
Key Characteristics of Actions:
Task Execution: Actions perform a specific task, such as sending an email, creating a new record, updating a database, or posting a message in a chat app.
Response to Triggers: They respond to the trigger event that starts the workflow. For example, if a trigger detects a new booking, an action might create an invoice in another system.
Customisable: You can configure actions to include specific details, like mapping fields from the trigger data to the target app.
Multi-Step Zaps: A Zap can include multiple actions, allowing you to chain several tasks together in a single automation.
You can learn how to best optimise your Zaps by checking Zapier's Help Center articles.
You are now ready to create automated workflows that can be set up in minutes without coding. Furthermore, you can streamline daily tasks and connect apps that wouldn’t normally integrate.