Kintaba Help & Documentation

Kintaba Documentation

Welcome to the Kintaba's documentation hub. You'll find comprehensive guides and documentation to help you start working with Kintaba as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Automations

Automations make it easy to create If-This-Then-That style actions that run within your incidents automatically.

With Automations, you can automate business logic like:

  • Make certain that specific oncalls are added when a tag or severity level is assigned to an incident
  • Add tags based on other tags.
  • Subscribe specific people based on the organization an incident is filed within

Viewing Automations

Automations are available to all users from the left-side bar under the Company heading.

Click the Automations link to load the automations configuration screen.

Here, you can see and edit all your active and inactive automations.

Adding a new Automation

To add a new automation, click the New Automation link in the upper left of the Automations center.

The launches the Create Automation modal.

You can now configure your automation by setting Conditions and Actions to be taken when those conditions are met.

📘

Automations can run on closed incidents

By default, automations are set to run only on Open incidents to prevent them from running on previously closed incidents unexpectedly. You can remove or change this condition, but be mindful of the impact on closed or mitigated incidents at all times!

Running automations every time vs. once

Automations can be configured to run every time the conditions match, or only once per incident. It is important to be mindful of whether you want the automation to continually enforce its rules, or only enforce them a single time

Consider the following two examples:

Example 1:

  1. An automation is created that adds a tag major outage whenever an incident is a SEV1
  2. The incident becomes a SEV1 and the tag major outage is added
  3. The incident is downgraded to a SEV2 and the tag major outage is manually removed
  4. Later, the incident is upgraded to a SEV1 again

If the automation is set to run once, no action will be taken at the end of this sequence.
If the automation is set to run every time, the tag major outage will be re-added.

Example 2:

  1. An automation is created that adds a tag major outage whenever an incident is a SEV1
  2. The incident becomes a SEV1 and the tag major outage is added
  3. The tag major outage is manually removed

If the automation is set to run once, no action will be taken at the end of this sequence.
If the automation is set to run every time, the tag major outage will be re-added.

Activating / Deactivating

Existing automations can be activated and deactivated from the configuration modal by clicking the "Deactivate Automation" or "Reactivate Automation" link.

Automations in Incidents

When automations are triggered, they appear in incidents with the Automations tag to make it clear that an automation took the action.

The actor for automations is the person who triggered the automation. For example, in the screenshot above, John Egan added the Compliance tag which triggered the automation, so John Egan is shown as the actor.

Updated 4 months ago

Automations


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.