POPOOpenPlatformMessageCardApi Trigger icon

POPOOpenPlatformMessageCardApi Trigger

Starts the workflow on a popo update

POPOOpenPlatformMessageCardApi Trigger

AI-generated

Overview

This node acts as a webhook trigger for the POPO Open Platform Message Card API. It listens for incoming HTTP requests (GET or POST) and processes encrypted data sent to it. The node decrypts incoming messages using AES encryption and can respond immediately, respond with data from the last executed node, or delegate the response to a separate 'Respond to Webhook' node. It is useful for workflows that need to handle secure webhook callbacks from the POPO platform, such as receiving message card updates or notifications.

Use Case Examples

  1. A workflow that triggers when a new message card update is received from the POPO platform, decrypts the payload, and processes the data.
  2. A workflow that responds immediately to webhook calls with a custom HTTP status and response body.
  3. A workflow that waits for all nodes to finish and then returns the last node's data as the webhook response.

Properties

Name Meaning
Respond Determines when and how the node responds to the webhook request. Options include responding immediately, responding with the last node's data, or using a separate 'Respond to Webhook' node.
Response Code The HTTP response code to return when responding immediately or with last node data.
Response Data Specifies what data to return when responding with the last node's data. Options include all entries, first entry JSON, first entry binary, or no response body.
Property Name (responseBinaryPropertyName) The name of the binary property to return when responding with binary data from the first entry.
Options Additional options such as whether to receive binary data, binary property name, ignoring bots, sending no response body, raw body handling, custom response data, response content type, response headers, and property name for response data.

Output

JSON

  • json
    • headers - Headers of the incoming webhook request.
    • params - URL parameters of the incoming webhook request.
    • query - Query parameters of the incoming webhook request.
    • body - Body of the incoming webhook request, decrypted if encrypted.

Dependencies

  • An API key credential for the POPO Open Platform Message Card API

Troubleshooting

  • Ensure the AES key used for decryption is correct and matches the one configured in the POPO platform credentials.
  • If the webhook does not trigger, verify the webhook URL is correctly registered with the POPO platform.
  • Check that the response mode is correctly set according to the desired response behavior.
  • If binary data is expected, ensure the binary data options and property names are correctly configured.

Links

Discussion