List transactions from polling bucket action

Use the List transactions from polling bucket action to retrieve transactions from a specific polling bucket (communication channel) in Orderful.

Input

Input field	Description
Bucket ID	Enter the unique identifier of the polling bucket (communication channel) you plan to retrieve transactions from.
Limit	Specify the maximum number of transactions to retrieve. The default is 30 and maximum is 100.
Message schema	This dynamically returns the output fields based on transaction type. Workato recommends copying the JSON output from this action to build the output schema.

Output

Output field	Description
Transaction ID	Unique identifier of the transaction.
URL	The full API endpoint URL for the transaction resource.
Version	API version used. For example, v3.
Sender	Object containing details about the sender trading partner.
Interchange control header (ISA) ID (Sender)	Sender’s interchange control header ID.
Interchange control header (ISA) ID qualifier (Sender)	Qualifier for the sender’s interchange control header ID.
Test interchange control header (ISA) ID (Sender)	Test sender interchange control header ID.
Test interchange control header (ISA) ID qualifier (Sender)	Qualifier for the test sender’s interchange control header ID.
Name (Sender)	Name of the sender trading partner.
Receiver	Object containing details about the receiver trading partner.
Interchange control header (ISA) ID (Receiver)	Receiver’s interchange control header ID.
Interchange control header (ISA) ID qualifier (Receiver)	Qualifier for the receiver’s interchange control header ID.
Test interchange control header (ISA) ID (Receiver)	Test receiver interchange control header ID.
Test interchange control header (ISA) ID qualifier (Receiver)	Qualifier for the test receiver’s interchange control header ID.
Name (Receiver)	Name of the receiver trading partner.
Type	Object describing the transaction type.
Name (Type)	Transaction type, such as 850_PURCHASE_ORDER. Refer to Orderful's documentation for more information about available transaction types (opens new window).
Stream	The stream that the transaction belongs to. For example, test refers to your testing environment and live refers to your production environment.
Business number	Business number associated with the transaction.
Reference identifiers	List of reference identifiers tied to the transaction.
Message	Object containing a link to the transaction message.
href (Message)	API endpoint URL for the transaction message.
Validation status	Status of EDI validation, such as VALID or INVALID. Refer to Orderful's documentation for more information about transaction statuses (opens new window).
Delivery status	Status of delivery to the trading partner, such as SENT or FAILED. Refer to Orderful's documentation for more information about transaction statuses (opens new window).
Acknowledgment status	Status of acknowledgment, such as ACCEPTED or REJECTED. Refer to Orderful's documentation for more information about transaction statuses (opens new window).
Created at	Timestamp when the transaction was created.
Last updated at	Timestamp when the transaction was last updated.
Acknowledgment	Object containing acknowledgment details.
URL (Acknowledgment)	API endpoint URL for the acknowledgment, if available.
Delivery	Object containing delivery details.
Delivery ID (Delivery)	Unique identifier of the delivery. You can map the Delivery ID datapill into the Approve delivery or Fail delivery actions to approve or fail a delivery.
URL (Delivery)	API endpoint URL for the delivery.
Approve (Delivery)	Object containing the API endpoint URL to approve the delivery.
URL (Approve)	API endpoint URL to approve the delivery.
Fail (Delivery)	Object containing the API endpoint URL to fail the delivery.
URL (Fail)	API endpoint URL to fail the delivery.