Channels actions
Actions allow real-time communication through HTTP requests.
- They are usually triggered by an event like a comment being posted to a blog.
- When that event occurs, the source site makes an HTTP request to the URL configured for the action.
- Users can configure them to cause events on one site to invoke behavior on another.
- To separate API calls from each other, you have to create individual API keys for each action.
Add action - Channels
Required
-
Name
Here you can name your channel action -
Event ID
An "event ID" for an action call is a unique identifier assigned to each specific event or action that triggers the action.
• It helps to track and manage different events sent by the actions to your system.
• This ID allows you to identify and handle each event individually, ensuring that you can properly process and respond to the data or action associated with that event.
• Essentially, it's like a reference number that helps you organize and understand the flow of information coming from actions.This event ID must be individual. -
Action type
Channel PriorityHere you can read more about channel priority: MISSING LINK
Channel SaturationHere you can read more about channel saturation: MISSING LINK
Enable channelEnables the selected channel(s)
Disable channelDisables the selected channel(s)
-
Target type
If you choose channel, you have to select the affected channel from the selector.
If you choose channel tag, you have to add tags to identify channels, and decide whether the channels have to contain all tags you defined or it is enough if at least 1 tag matches. -
Target
Select the target channel for the action(Later it will be more than 1 target)
Optional
-
Teams
Here you can select teams to manage and see the datasourceThis option is only available if the customer has at least one team available.
How to trigger action?
Create an API key
Here you can read more about the API key creation: MISSING LINK
Generate example link
By clicking on the Generate example link
button a modal will open.
Here's what you need to fill in the Generate example link
in order to successfully complete the action.
API key | Priority | Saturation | |
---|---|---|---|
Change priority of channel | ✔️ | ✔️ | ☓ |
Change saturation of channel | ✔️ | ☓ | ✔️ |
Enable Channel | ✔️ | ☓ | ☓ |
Disable Channel | ✔️ | ☓ | ☓ |
-
API key ⟶
Always required
An API key is essential for a webhook call as it serves as a unique identifier, ensuring that the request is authenticated and authorized. This helps maintain security by verifying that the request is coming from a trusted source, preventing unauthorized access and potential misuse of the webhook. -
Priority / Saturation - Value box ⟶
Only available if the action requires an unique value for successful modification.
In this box you have to define a value, what will be sent to the target.
After you filled all the necessary information, you can decide what do you wish to do with the action:
-
Copy link
After you filled every necessary boxes, you can create a webhook call link, that you can use inside contents as touch actions. -
Test
After you filled every necessary boxes, you can test the action on the selected target.
Ⓘ CLICK HERE FOR RELATED ARTICLES