Actions69
- 👤 Customer Actions
- 🛍️ Product Actions
- 📄 Customer Invoice Actions
- 💰 Quote Actions
- 🏢 Supplier Actions
- 📥 Supplier Invoice Actions
- 🏦 Bank Account Actions
- 💸 Transaction Actions
- 💰 Payment Actions
- 💳 SEPA Mandate Actions
- 🔄 GoCardless Mandate Actions
- 📓 Journal Actions
- 📈 Ledger Account Actions
- 📋 Ledger Entry Actions
- 📑 Ledger Entry Line Actions
- 📎 Ledger Attachment Actions
- ⚖️ Trial Balance Actions
- 📅 Fiscal Year Actions
- 🏷️ Category Actions
- 📦 Category Group Actions
- 🔄 Billing Subscription Actions
- 📋 Invoice Lines Actions
- 📎 Invoice Appendices Actions
- 📎 File Attachment Actions
- 📄 Commercial Document Actions
- ⚡ E-Invoice Create (Import) Actions
- 👤 User Profile Actions
📑 Ledger Entry Line → Get All
AI-generatedSummary
Retrieve all ledger entry lines from Pennylane, emitting each entry as a separate n8n output item.
Inputs
- resource — Resource selector; fixed to Ledger Entry Line for this operation. Visible in the node UI under 📑 Ledger Entry Line.
- operation — Operation selector; fixed to Get All for this operation. Visible in the node UI.
Output shape
Individual ledger entry line objects, one per output item. If the Pennylane API response includes metadata fields (source, total_payments, generated_at), they are attached as _source, _total_payments, and _generated_at respectively on each output item.
The node auto-splits the API response: each ledger entry line in the returned items array becomes its own n8n output, enabling downstream nodes to process entries individually rather than handling a single JSON array.
Examples
Example 1: A workflow fetches all ledger entry lines and routes each through a different accounting validation node.
Node set to resource: 📑 Ledger Entry Line, operation: Get All. No additional parameters required. Each output item contains the line's data plus optional metadata from the API response.