Help & Support

Automations

Streamline Your Workflow


Automations

help streamline repetitive tasks by automatically performing actions when certain events occur in your collections .

By defining the 'When → Then' conditions, you can reduce manual work and keep your team in sync.

What are automations?

Automations let you configure trigger events (the 'when') and resulting actions (the 'then'). For example:

  • When a new record is added to a 'Maintenance' collection → Then create a task assigned to multiple maintenance staff, or send a notification
  • When a workflow stage changes to 'Approved' → Then generate a new record in another collection, or send an email alert

Benefits of automations

  • Automate routine tasks like creating follow-up tasks or notifications
  • Make sure boring administration tasks are never missed
  • Standardise processes and reduce manual steps
  • Keep everyone informed with automated alerts or tasks
  • Add new automations as your organisation's needs evolve

Setting Up an Automation

1. Access Automation Settings

  1. Open Settings: Click your name in the bottom-left corner of Kinabase
  2. Select Automations: Under Organisation, choose Automations
  3. Add New Automation: Click + Add Automation in the top-right corner
  4. Name & Description: Give your automation a clear name (e.g., 'Notify Finance on New Invoices') and a brief description

2. Define the 'When' Condition(s)

This is your 'Trigger' - when this happens, the automation runs.

You have lots of options for trigger events, for instance:

  • A record is added to a specific collection
  • A record is updated (general or a specific field)
  • A record is right-clicked (context menu)
  • A record becomes due (if you have a date field in your record)
  • A record changes workflow stage

Pick your trigger event from the dropdown menu.

You can also set Additional Trigger Conditions based on field values using the 'If field value is...' option.

Additional trigger conditions allow you to refine when automations run:

  • Define 'If' conditions with both '+And' and '+Or' criteria
  • Use previous field values to trigger on changes (e.g., 'Previous Status' is 'Pending' and 'New Status' is 'Approved')
  • Use field character length for text fields
  • For example, 'Only if priority equals High and Company is XYZ'

3. Set the 'Then' Action

Once you define the trigger, choose what Kinabase should do automatically from the Action Type dropdown:

  • Add a Task: Create and assign tasks, optionally setting due dates or multiple assignees
  • Send a Notification: Choose recipients and urgency (Urgent, High, Medium, Low)
  • Create a New Record: Specify a target collection and fill out relevant fields
  • Update the Current Record: Change fields in the same record that triggered the automation
  • Update portal access: Automatically invite, grant, or revoke portal access for external user records
  • Send an Email: Send automated emails to specified recipients
  • Generate PDF Document: Create PDF documents from templates
  • Call External API: Send data to external systems via webhooks

You can add multiple steps to the same automation - e.g., first send a notification, then create a new record, then add a task.

4. Save & Activate

  • Click 'OK' to finalise your automation
  • It takes effect immediately; any new triggers will now run the automation steps you defined

Action Options

Kinabase has a variety of action types to choose from when setting up your automations. Each action type has its own configuration options to tailor the automation to your needs.

Add a Task

The Add a Task action creates and assigns a follow-up task automatically, with optional due dates and multiple assignees.

How to configure:

  1. Enter the task title and any instructions your team needs to complete the work.
  2. Select one or more assignees who should own the task.
  3. Set an optional due date or timing rule so tasks are created with clear deadlines.
  4. Save the step and test that task details are populated as expected.

How to use this action:

  • When ...a support case is marked Escalated,
    then ...create a task for the on-call manager due in 2 hours.
  • When ...a proposal reaches Contract Review,
    then ...create tasks for both Legal and Sales Ops.
  • When ...a new customer is onboarded,
    then ...create a setup task for the implementation specialist.

Send a Notification

The Send a Notification action sends an in-app alert to selected users and lets you set urgency (Urgent, High, Medium, or Low).

How to configure:

  1. Choose who should receive the notification (specific users, teams, or relevant owners).
  2. Write the notification content so recipients know exactly what changed.
  3. Set the urgency level: Urgent, High, Medium, or Low.
  4. Save and verify the right people are notified when the trigger runs.

How to use this action:

  • When ...an invoice becomes overdue,
    then ...send a high urgency notification to Finance.
  • When ...a deal value is changed above a defined threshold,
    then ...notify the team lead.
  • When ...a milestone due date is moved,
    then ...alert the project manager.

Create a New Record

The Create a New Record action inserts a record in another collection (including subcollections) and maps values from the triggering context.

How to configure:

  1. In In Collection, choose the target collection (subcollections are shown with their parent collection name, e.g. "Customer - Orders").
  2. Map each field using a fixed value or copied value from the triggering record context.
  3. If targeting a subcollection, configure the required (Parent) field using Link to current record, Copy from context, or Set a fixed value.
  4. Save the step only after validation passes; Kinabase blocks saving until required parent assignments are valid.

How to use this action:

  • When ...a new project is approved,
    then ...create a kickoff record in a Project Milestones subcollection linked to that project.
  • When ...a lead is qualified,
    then ...create a new customer record and copy key contact details.
  • When ...an order is confirmed,
    then ...create related fulfillment records automatically.

Update the Current Record

The Update the Current Record action changes fields on the same record that triggered the automation.

How to configure:

  1. Select the field or fields to update on the triggering record.
  2. Set each new value using fixed values, copied values, or expressions.
  3. Review dependencies so the update does not conflict with other automations on the same record.
  4. Save and confirm the expected fields are updated after the trigger event.

How to use this action:

  • When ...a quote is accepted,
    then ...set Status to "Won" and set Won Date to today.
  • When ...a task is completed,
    then ...set Progress to 100% and clear the Blocked Reason field.
  • When ...a record moves to Cancelled,
    then ...set Active to "No".

Update portal access

The Update portal access action automates invite, grant, or revoke access for external user

records in your portal .

How to configure:

  1. Confirm the automation collection is configured as the user collection for an external portal.
  2. Select the target portal if your environment has multiple external portals.
  3. Choose one action: Send invite (grant access + email), Grant access (without email), or Revoke access.
  4. Save the step; repeat grant/revoke operations are handled safely so workflows continue without failing.

How to use this action:

  • When ...a client record moves to Active,
    then ...send a portal invite automatically.
  • When ...an account reaches Offboarded,
    then ...revoke portal access immediately.
  • When ...onboarding is handled manually for approved partners,
    then ...grant portal access without sending an invite email.

Send an Email

The Send an Email action sends an automated email to defined recipients using your configured email settings.

How to configure:

  1. Choose recipients (for example, record contacts, internal users, or fixed email addresses).
  2. Set the subject and email content, including mapped record values where needed.
  3. Confirm the sender/account configuration used for outbound email delivery.
  4. Save and test that recipients, subject, and body render correctly.

How to use this action:

  • When ...a booking record is created,
    then ...send a confirmation email to the customer.
  • When ...a renewal date is 30 days away,
    then ...email the account owner.
  • When ...status changes to overdue,
    then ...send a missed-payment reminder to the billing contact.

Generate PDF Document

The Generate PDF Document action creates a PDF from a template using data from the record and related fields.

How to configure:

  1. Select the PDF template you want to use for this automation step.
  2. Map template fields to values from the triggering record and related data.
  3. Configure naming and destination options based on how your team stores generated documents.
  4. Save and preview output to confirm formatting and data placement.

How to use this action:

  • When ...a billing record moves to Ready to Send,
    then ...generate an invoice PDF.
  • When ...a project status changes to Completed,
    then ...create a signed-off project summary PDF.
  • When ...a training record is marked as passed,
    then ...produce a completion certificate PDF.

Call External API

The Call External API action posts automation data to an external endpoint so other systems can react in real time.

How to configure:

  1. Enter the endpoint URL and select the request method required by the external system.
  2. Configure headers, authentication, and payload mapping from record fields.
  3. Review response and failure behaviour using automation logs so errors can be diagnosed quickly.
  4. Save and run a controlled test before enabling the automation in production.

How to use this action:

  • When ...a new order is created,
    then ...push order data to a fulfillment platform via webhook.
  • When ...plan fields change,
    then ...send updated subscription details to the billing system.
  • When ...a lead is converted,
    then ...notify the CRM integration.

Advanced Automation Features

Multiple Steps & Conditions

Enable a cascade of action steps based on your conditions and logic:

Adding Steps: Create multiple follow-up actions. For example, after adding a task, you could also send an email notification to a manager.

Filters & Conditions: Some triggers allow you to refine when an automation runs (e.g., only if a certain field equals 'High Priority').

Conditional & Filter Configuration

You can apply detailed filter conditions to make multi-step automations more precise, including record-copy scenarios.

For Create a New Record steps using Related Record Copying, configure filters so only matching source records are copied:

  1. In a Create a New Record step, scroll to Related Record Copying and choose your source and target collections.
  2. Click Add filter under the source collection and link field selectors.
  3. Build conditions by selecting a source field, operator, and value.
  4. Add additional conditions with And or Or if as needed.
  5. Save the automation; only records matching the filter will be copied when it runs.

The step summary shows a plain-English filter description, making it easier to review what the automation will copy.

Note: conditions that depend on the current user are not available here, because automations may run without a logged-in user context.

Browse our Product Updates for the latest release notes on automation filters.

Preview Automations

Some workflow stages allow you to preview which automations will run. This ensures you have full clarity on what will happen next.

Use this preview feature to confirm tasks, notifications, or record changes before finalising an action.

Assign Tasks to Multiple Users

When adding an 'Add a Task' step, you can select multiple owners. All assigned users will be notified and see the task in their dashboard

.

AI-Generated Descriptions

You can generate a human-readable description for any automation using AI. In the automation editor, a bolt icon appears beside the Description field. Click it, and Kinabase analyses the automation's trigger, steps, field assignments, and conditions to produce a concise summary in plain English. The description is written for a general audience, so anyone on your team can understand what the automation does without reading through every step.

The AI considers the full configuration when generating a description, including:

  • Trigger type — what event starts the automation and which collection it applies to
  • Step details — the type of each action (e.g. create a record, add a task, send a notification, send an email, generate a PDF, call an external API)
  • Field assignments — which fields are set and how their values are determined (copied from another field, set to a fixed value, or calculated from an expression)
  • Conditional logic — any if/else branches and the conditions that control which steps run

The bolt icon only appears when the automation has a valid trigger and no configuration errors. If you do not see it, check that your trigger and steps are fully configured.

You can edit the generated description, regenerate it after making changes, or replace it with your own text at any time.

Read our Product Update for more details.

Linked Records

You can copy parent-record values automatically in automation field mapping.

When creating or editing an automation, you can set fields in the new record to pull values from the triggering record or other related records:

  1. In the Automation Editor, add or open a Record step that targets a sub-record collection
  2. In Field assignment, click the "Copy from parent" option next to any mappable field
  3. Choose the parent field you want and Save – Kinabase will use that value every time the step runs

Read our Product Update for more.


Running Automations on Multiple Records

Context menu automations can be run on multiple records at once, allowing you to process batches of data in a single action rather than clicking through each record individually.

How to run automations on multiple records

  1. Navigate to a collection and select multiple records using checkboxes or Shift-click to select a range
  2. Right-click to open the context menu and look for your automation under the available actions
  3. Review the preview modal, which shows:
    • Records selected: Total number of records you've selected
    • Will run: Records that match your automation's filter criteria
    • Filtered out: Records excluded based on your automation's conditions
  4. Click Run to execute the automation across all matching records
  5. Review the results summary showing how many records completed successfully, failed, or were filtered out

Important notes

  • Automations that include form steps will not appear in the multi-record menu, as forms require individual input for each record
  • The preview helps you understand which records will be processed before you commit
  • Any failures display the record name and error message for easy troubleshooting
  • Multi-record automations are available on Pro, Charity, and Enterprise plans

Browse our Product Updates for the latest release notes on multi-record automations.


Viewing & Editing Automations

Edit or Deactivate: If you need to pause or change an automation, open it from the Automations list and modify or toggle it off.

View History Logs: Right-click and edit an automation. Select the History tab to see a log of each time it's been triggered and the outcome. You will also find statistics on how many times it has run successfully or failed.

View Schedule: If your automation is based on times and dates, you can see when it is next scheduled to run in the 'Scheduled' tab.


Best Practices

Automations can be very useful, but can become overly complicated if you're not careful. Follow the guidance below to get the most out of them:

Start simply & evolve

Start with a minimal number of automations. Overcomplicating from the get-go can lead to confusion.

It does 'what it says on the tin'

Clear automation names help your team understand their purpose straight away.

Periodically review

Check automation logs periodically to ensure everything is running smoothly.

Combine with your workflows

Automations work great with workflows - when a record moves to a certain stage, let an automation handle the follow-up tasks.


Using Automations in Kinabase saves time and maintains consistency for your team, letting them focus on the tasks that matter most.

If you need more help or have advanced scenarios in mind, check out our other guides or contact our Support Team.