Definition Automations

Overview

Every definition (content type) in Qik can have automations configured directly on it. These automations run automatically when content of that type is created, updated, or deleted. This is different from the Developer section's listeners and triggers — definition automations are configured on the definition itself and are tightly integrated with the content lifecycle.

Types of Automation

There are four types of definition automation:

1. Notifications

Automatically notify specific people when content is created or modified.

• Recipients — Select which profiles should receive the notification
• Filter — Optionally set conditions for when the notification should fire (e.g. only when status changes to 'urgent')
• Triggers — Which events fire the notification (create, update, delete)

Notifications are delivered as emails or in-app notifications to the configured recipients.

2. Actions

Automatically run a custom action when content is created or modified.

• Action — Select which action to run (from your Developer actions)
• Filter — Conditions for when the action should execute
• Triggers — Which events fire the action (create, update, delete)

This is a powerful way to connect your custom business logic to content changes without needing to set up a separate listener.

3. Workflows

Automatically create a workflow card when content of this type is created.

• Workflow — Select which workflow definition to create a card in
• Filter — Conditions for when a card should be created

This is commonly used for form submissions — when someone submits an application form, a workflow card is automatically created in your review pipeline.

4. Confirmations

Automatically send a confirmation email when content is created (typically used for form submissions).

• Email template — Select an email definition to use as the template
• Sender details — Configure the from name and email address
• Subject — The email subject line
• Filter — Conditions for when the confirmation should send

Confirmations are ideal for acknowledging form submissions, registration sign-ups, or any content creation that should trigger a response to the submitter.

Configuring Automations

To add automations to a definition:

1. Open the definition editor (from Content or the content type's settings)
2. Navigate to the Automation section
3. Add the type of automation you want (notification, action, workflow, or confirmation)
4. Configure the recipients, actions, filters, and triggers
5. Save the definition

Filters on Automations

Each automation supports optional filters that control when the automation fires. Without a filter, the automation runs every time the trigger event occurs. With a filter, it only runs when the content item matches the specified conditions. For example, you might only send a notification when a form submission includes a value above a certain threshold.

Common Patterns

• Form → Notification + Workflow — When a form is submitted, notify the review team and create a workflow card for processing
• Form → Confirmation — Send the submitter an acknowledgement email
• Content → Action — When content is updated, run an action that syncs the data to an external system
• Event → Notification — When a new event is created, notify relevant team members

FAQs