Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kimp360.com/llms.txt

Use this file to discover all available pages before exploring further.

An action in Zapier is a task that Zapier performs automatically after a trigger event occurs. Actions are the steps that make your Zap do useful work in your connected apps, such as KIMP360.

​
What is an Action?

  • An action is a task that Zapier carries out in response to a trigger.
  • After your Zap is triggered (for example, by a new card in KIMP360), Zapier will perform the actions you have set up, such as creating a record, sending a message, or updating data.
  • Each Zap can have one or more actions.
Example: If your Zap is triggered by New Card Created in KIMP360, you can set up an action to automatically add the card details to a Google Sheet or send a notification to your team.
**Example:**If you use the KIMP360 Slack app, you can create a new card directly from Slack using a slash command (for example, /KIMP360 create-card). This can trigger a Zap that automatically adds the card to your KIMP360 board, making it easy to turn Slack conversations into actionable tasks without leaving your chat.
An action always runs after a Zap trigger. For example:
  • When a form is submitted in another app, create a new KIMP360 task.
  • When a KIMP360 task is archived, update a record in your CRM.
  • When a new customer is added in your billing tool, create a brand and tags.

​
Prerequisites

Before you can use any KIMP360 action in Zapier, make sure you have:
  • Installed the KIMP360 Zapier app in your Zapier account.
  • Generated a KIMP360 API key from your dashboard.
  • Connected your KIMP360 account in Zapier using that API key.
See Zapier App Authentication for step‑by‑step instructions and screenshots.

​
How KIMP360 actions fit into a Zap

Every KIMP360 action is added as a step in your Zap:
  1. Start with a trigger (for example, “New row in Google Sheets” or “New card created in KIMP360”).
  2. Add a KIMP360 action step to perform work inside your KIMP360 account.
  3. Map fields from your trigger (or previous steps) into the KIMP360 action fields. [image]
Each individual action page further explains how to configure its fields (Configuration).
You always need at least one trigger step before adding a KIMP360 action. Triggers define when the Zap runs; actions define what happens inside KIMP360.