[ Content and files ]
Klipy integration for your workflows.
Connect Klipy to Collabase once and use 4 actions in your workflows. No code needed, hosted in Switzerland.
Klipy in Collabase
Connect Klipy to Collabase once and use 4 actions in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Search and retrieve GIFs, stickers, and video clips from KLIPY's media library.
How to connect it
- Open the integrations in the workspace settings.
- Choose Klipy and connect your account.
- Add a trigger or an action to the workflow.
- Sign in to your KLIPY account at https://klipy.com
- Go to your dashboard and open API Settings
- Copy your App Key
Klipy triggers
Klipy does not start a workflow on its own. You use its actions after any other trigger.
Klipy actions
| Name | Description | Fields |
|---|---|---|
| Search GIFs | Search and retrieve GIFs from KLIPY's database by keyword or phrase. |
+ 1
|
| Search Stickers | Search and retrieve stickers from KLIPY's database by keyword or phrase. |
+ 1
|
| Search Clips | Search and retrieve video clips from KLIPY's database by keyword or phrase. |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Content and files ]
Related integrations
Tools that often share a workflow.
Questions about Klipy
What can I automate with Klipy in Collabase?
Klipy brings 4 actions and 0 triggers, for example Search GIFs, Search Stickers, Search Clips and Custom API Call. You combine them in a workflow without code and mix them with every other integration.
How do I connect Klipy to Collabase?
You open the integrations in the workspace settings, choose Klipy and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Does the Klipy integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.