Orderful Poller icon

Orderful Poller

Poll for new transactions from Orderful
Join our community

Actions2

Overview

The Orderful Poller node is designed to interact with the Orderful API to poll for new transactions or remove existing transactions from a specified poller bucket. It supports two main operations:

  • Get Transactions: Retrieves transactions from a named poller bucket, optionally filtered by transaction type or trading partner ID, and limited in number.
  • Remove Transactions: Removes specific transactions from a poller bucket by their IDs.

This node is useful in scenarios where you want to automate the retrieval and management of EDI (Electronic Data Interchange) transactions from Orderful, such as syncing transaction data into your workflow or cleaning up processed transactions.

Practical Examples

  • Automatically fetch the latest purchase orders (transaction type 850) from a specific bucket to process them downstream.
  • Remove transactions that have been successfully processed to keep the poller bucket clean and avoid duplicate processing.

Properties

Name Meaning
Bucket Name The name of the poller bucket to query or modify.
Additional Fields Optional filters and limits for fetching transactions:
- Limit: Max number of results to return.
- Transaction Type: Filter transactions by type code (e.g., "850", "810").
- Partner ID: Filter transactions by trading partner ID.

Output

The node outputs an array of JSON objects representing the transactions retrieved or the result of the removal operation.

  • For Get Transactions, the output JSON contains the list of transactions matching the criteria from the specified bucket.
  • For Remove Transactions, the output JSON reflects the response from the API after attempting to remove the specified transactions.

If an error occurs during execution and the node is configured to continue on failure, the output will include an object with an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Orderful API.
  • The base URL for the Orderful API must be configured in the credentials.
  • Uses HTTP requests with JSON payloads to communicate with the Orderful service.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key or base URL in credentials will cause authentication failures.
    • Specifying a non-existent bucket name will result in errors or empty results.
    • Providing invalid transaction IDs for removal may cause partial or complete failure of the remove operation.

  • Error Messages:

    • Errors returned from the API are surfaced as node errors with messages indicating the problem (e.g., unauthorized, not found).
    • If "Continue On Fail" is enabled, errors are returned as JSON objects with an error property instead of stopping execution.

  • Resolution Tips:

    • Verify API credentials and permissions.
    • Double-check bucket names and transaction IDs.
    • Use the "Limit" field to control the volume of data fetched and avoid timeouts.

Links and References

Discussion