Orderful Poller icon

Orderful Poller

Poll for new transactions from Orderful
Join our community

Actions2

Overview

The "Orderful Poller" node interacts with the Orderful API to manage transaction data within poller buckets. Specifically, it supports two main operations: retrieving transactions from a specified bucket and removing transactions from a bucket by their IDs.

This node is beneficial in scenarios where users need to automate the monitoring and management of transaction data flowing through Orderful. For example, a user might regularly fetch new transactions for processing or clean up processed transactions by removing them from the poller bucket to avoid duplication.

Practical examples:

  • Automatically fetching the latest 50 transactions of a certain type from a specific bucket for downstream processing.
  • Removing a set of processed transaction IDs from a bucket to keep the poller state clean.

Properties

Name Meaning
Bucket Name The name of the poller bucket to interact with (e.g., "default").
Transaction IDs Comma-separated list of transaction IDs to remove from the specified bucket.

Output

The node outputs JSON data representing the result of the requested operation:

  • For Get Transactions: An array of transaction objects retrieved from the specified poller bucket, filtered optionally by limit, transaction type, and partner ID.
  • For Remove Transactions: A response object indicating the success or failure of the removal request for the specified transaction IDs.

The output is structured as an array of JSON objects, each corresponding to an input item processed. There is no binary data output.

Dependencies

  • Requires an API key credential to authenticate requests to the Orderful API.
  • Needs the base URL of the Orderful API configured in credentials.
  • Uses HTTP methods GET and POST to interact with /poller/{bucketName} endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect bucket names may lead to 404 errors or empty results.
    • Providing malformed or non-existent transaction IDs when removing transactions can cause errors or no effect.

  • Error messages:

    • Errors returned from the API are captured and surfaced as node execution errors.
    • If "Continue On Fail" is enabled, errors for individual items are returned in the output JSON under an error field.

  • Resolutions:

    • Verify that the API key and base URL are correctly configured.
    • Double-check bucket names and transaction IDs for correctness.
    • Use the "Continue On Fail" option to handle partial failures gracefully.

Links and References

Discussion