Erply Trigger icon

Erply Trigger

Use Erply Webhooks

Erply Trigger

AI-generated

Overview

This node acts as a webhook trigger for Erply, a retail management platform. It listens for specific events (Insert, Update, Delete) on a specified database table within Erply and triggers workflows when those events occur. This is useful for automating processes based on real-time data changes in Erply, such as syncing inventory updates, customer data changes, or sales transactions to other systems.

Practical examples:

  • Trigger a workflow whenever a new product is inserted into the Erply product table.
  • Start an automation when a customer record is updated.
  • React to deletion of records to maintain data consistency across platforms.

Properties

Name Meaning
Table The name of the Erply database table to monitor for changes.
Action The type of event to listen for on the table. Options: Insert, Update, Delete.
Secret A secret key used for securing the webhook communication with Erply.
Include Headers Whether to include HTTP headers in the output response.
Base URL The base URL of the Erply webhook service endpoint (default: https://webhook.erply.com).
JMES Path A JMESPath expression to extract specific parts of the incoming webhook JSON payload.

Output

The node outputs JSON data representing the items received from the Erply webhook. Specifically, it extracts the array at the path items[].data by default, which contains the relevant data objects related to the triggered event.

If "Include Headers" is enabled, the full HTTP response including headers can be returned.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with Erply's webhook configuration API.
  • Needs network access to Erply's webhook service at the configured Base URL.
  • Uses the external Erply API to register, check, and delete webhook configurations.

Troubleshooting

  • Webhook not triggering: Ensure the webhook is properly registered in Erply with correct table and action parameters. Use the node’s webhook existence check method.
  • Authentication errors: Verify that the provided secret key and API credentials are correct and have sufficient permissions.
  • Incorrect data extraction: If the output JSON does not contain expected data, adjust the JMESPath property to correctly target the desired part of the webhook payload.
  • Failed webhook registration: Network issues or invalid parameters may cause webhook creation to fail. Check connectivity and parameter correctness.
  • Unexpected empty payloads: Confirm that Erply is sending data for the specified table and action.

Links and References

Discussion