[ Communication ]
Line Bot integration for your workflows.
Connect Line Bot to Collabase once and use 2 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.
Line Bot in Collabase
Connect Line Bot to Collabase once and use 2 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Build chatbots for LINE
How to connect it
- Open the integrations in the workspace settings.
- Choose Line Bot and connect your account.
- Add a trigger or an action to the workflow.
- Open the LINE Developers Console and pick your Messaging API channel.
- Go to the Messaging API tab.
- Under Channel access token (long-lived), click Issue and copy the token.
Line Bot triggers
| Name | Description | Fields |
|---|---|---|
| New MessageInstant via webhook | Starts the flow when your LINE bot receives a message. |
|
Line Bot actions
| Name | Description | Fields |
|---|---|---|
| Send Message | Send a text message to a LINE user or group chat. |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Communication ]
Related integrations
Tools that often share a workflow.
Questions about Line Bot
What can I automate with Line Bot in Collabase?
Line Bot brings 2 actions and 1 trigger, for example Send Message and Custom API Call. You combine them in a workflow without code and mix them with every other integration.
How do I connect Line Bot to Collabase?
You open the integrations in the workspace settings, choose Line Bot and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Can Line Bot start a workflow?
Yes. Line Bot provides 1 trigger, for example New Message. The workflow runs as soon as the event happens.
Does the Line Bot 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.