> For the complete documentation index, see [llms.txt](https://docs.cekat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cekat.ai/en/automation-and-developer/cekat-automations.md). # Cekat Automations ![Cekat Automations canvas](https://3693109682-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZNZlvyOVkZXyd3pz2Cql%2Fuploads%2FHPVDtTmX8cShDqFympDh%2Fcekat-automations-canvas-updated.png?alt=media) Cekat Automations connects customer activity to actions in Cekat and in external services, without you having to write code or manage API credentials by hand. Workflows follow a simple structure: > **When something happens -> check conditions if needed -> run an action** For example, a business can detect when someone submits a form, check the campaign or customer data, then send that information to Google Sheets or process it through a workflow in Cekat. ## Key features * Build workflows on a visual drag-and-drop canvas * Use Cekat events and business data as triggers * Add branches based on conditions * Work with Cekat resources such as conversations, inboxes, contacts, CRM data, labels, boards and fields * Run actions in Cekat automatically * Connect supported external services, such as Google Sheets and Gmail * Send form submissions to a spreadsheet * Run a workflow when someone clicks a WhatsApp link * Test workflows before you publish them * See execution status and run history * See which steps succeeded, failed, are pending or were skipped * Help prevent the same event from being processed more than once * Get clearer error details for troubleshooting ## Workflow building blocks ![Cekat Automations node picker](https://3693109682-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZNZlvyOVkZXyd3pz2Cql%2Fuploads%2F73wfHXneaen9wqpAGNsZ%2Fcekat-automations-node-picker-updated.png?alt=media) Every workflow is made up of one or more of these building blocks: | Building block | What it does | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | Trigger | The event that starts the workflow, for example a new message being received or CRM data being updated. | | If Condition | An IF/ELSE branch that checks a condition and sends the event down the right path. If the condition isn't met, the event follows the `Otherwise` path. | | Action | The action that runs, for example adding a label or updating the CRM. | Every workflow follows the same structure: **Trigger → Condition (optional) → Action** Example: > **Trigger:** New message received\ > **If Condition:** If the message came from the Sales inbox\ > **Action:** Add the `New Lead` label\ > **Otherwise:** Do nothing ## Example use cases ### Label conversations automatically When a new message comes in, an automation can check the inbox, contact data or any other available information, then apply the right label. > When a customer messages the Sales inbox -> add the `New Lead` label. ### Update CRM data When a conversation or customer data changes, an automation can update the related stage, pipeline status, field or CRM item. > When a customer confirms a purchase -> change the deal status to `Won`. ### Send reminders or follow-ups Automations can run actions on a schedule or when certain data changes. > When a lead hasn't been followed up within a set period -> create a reminder for the right team. Add suitable conditions so the same reminder or action doesn't run over and over. ### Connect Cekat to external services Data from Cekat can be passed on to supported services, such as Google Sheets or Gmail. > When a form is received -> add the customer's details to Google Sheets. ## A safer setup Cekat Automations uses structured, validated resource references, so you don't have to copy and paste IDs by hand. This helps prevent configuration mistakes, like picking the wrong CRM board or using an invalid label. Built-in Cekat actions also use your business's automatically verified connection, so there's no need to fetch or paste a Cekat API key. ## Create your first automation The video below shows how to open Cekat Automations from the Cekat home page and build a simple automation: > When a message is received -> if the message contains `halo` (hello) -> reply with `halo`. {% embed url="" %} 1. Open **Automations** from the Cekat home page. 2. Create a new automation as a draft. 3. Choose the **Message received** trigger. 4. Add an **If Condition** and set it so the message contains `halo`. 5. On the matching path, add an action that sends the message `halo`. 6. Test the workflow with safe test data. 7. Review which path ran and the result of each step. 8. Publish and turn on the automation once the test results look right. 9. Keep an eye on the first few runs in the run history. {% hint style="warning" %} Depending on how your workflow is set up, a test can run real actions. Use conversations, contacts or CRM data set aside for testing. Before you run a test, make sure the workflow won't accidentally message live customers or change their data. {% endhint %} ## Before you turn on an automation Make sure you've checked that: * The trigger uses the right inbox, board or resource * Each **If Condition** uses the right field, operator and value * Each **If Condition** path is connected to the right action * The `Otherwise` path has been reviewed and set up the way you need * Labels, agents, fields and other resources come from the right business * The workflow has been tested for cases that should run the action * The workflow has been tested for cases that should be skipped or follow a different path * The test results match what you expected If the first results in production aren't what you expected, turn the automation off and contact your Cekat PIC before running it again. ## Limitations * Cekat Automations is available on a limited basis to approved businesses. * To request access, contact your Cekat PIC: your Account Manager, Product Support or IT Delivery. * Once your request is approved, the Cekat team turns on access and gives you initial guidance on building and using automations. * Availability can vary from business to business, depending on workflow needs, configuration readiness and the onboarding process. * For now, Cekat Automations runs alongside your existing n8n workflows. You can migrate gradually, but automatic import of n8n workflows isn't supported yet.