Skip to main content

Overview

Triggers are the gateway to Kimiko as they allow you to create/log events.

What is a Trigger event?​

Conceptually, an Trigger event is a representation of something that has happend. That something could be a purchase made, a stage change in your CRM, a form submitted on your website, or any other action that occurs on the internet.

Triggers & Webhooks​

Many SaaS applications produce events and allow you to subscribe to real-time notifications of thee events by using Webhooks. Webhooks are essentially an HTTP request emitted when an event happens in a system.

Kimiko works quite well with webhooks. Whether your communication provider enables webhooks when you receive a new text message or your CRM provider emits webhooks when a new lead is added, Kimiko can consume these events using the Trigger API.

The benefits of using Kimiko as the destination for all of your SaaS webhooks include:

  • Separating the event from the automation. Events are pretty consistent but automations can change. Rather than hard-coding event logic into your automations, Kimiko allows you to manage the automation logic independent from the event logic.
  • Monitoring & debugging. Kimiko logs all of the events that triggered and gives you the ability to see what has happened over time. Kimiko comes with tools to "re-trigger" events to debug and test automations.
  • Connections. Kimiko Connections includes many SaaS applications. Rather than managing your API Keys and Oauth tokens for each SaaS application in each automation logic you create, Kimiko abstracts the key/token complexitites allowing you to quickly connect to various backend applications.