Skip to main content
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 (e.g., /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.
Stay tuned for a list of available Kimp360 actions and setup instructions!

​
Available Actions in Kimp360 Zapier Integration

Below are the actions you can use with the Kimp360 Zapier app. Each action allows your Zap to perform tasks in your Kimp360 account automatically.

​
Create Card

Creates a new card in your selected board under the Requests Status column. Use this action to automate adding new requests or tasks directly from other apps into your Kimp360 workflow. Create Card With Zapier With the Create Card action, you can automatically generate new requests or tasks in Kimp360 from any connected app in Zapier. When triggered, a new card is created in your selected board under the Requests status column. The selected content should be formatted as regular markdown text, not as a code block. Here’s the corrected formatting:

​
Card Fields Available

When creating a card, you can customize the following fields to fit your workflow:
  • Product – The product category (Graphic / Dev / Video) the card belongs to.
  • Card Title – A clear, descriptive name for the request.
  • Card Type – Specify the type of request (e.g., design, content, video).
  • Dimensions – Add required dimensions for the request in the format W x H.
  • File Formats – Indicate the file formats needed for the deliverable (e.g., JPEG, PNG)
  • Software – Mention any software requirements (e.g., Photoshop, Illustrator, Figma).
  • Card Description – Provide detailed instructions for the task.
  • Text Copy – Include any text content needed for the design.
  • Text Copy Files – Attach copy documents if applicable.
  • Brand – Specify the brand for which the task is being created.
  • Card Additional Files – Upload supporting assets.
  • Additional Files Notes – Add notes related to the supporting files.
  • Card Reference Files – Include reference images or documents.
  • Reference Files Notes – Add notes for reference materials.

​
Search Cards

Searches for cards in your board based on title, card ID, or status. This action helps you find and use specific cards in your Zaps, enabling advanced workflows like conditional logic or data lookups.