PennylaneInstall

Summary

Fetch all customers from Pennylane, auto-split into individual n8n outputs.

Inputs

• resource — Resource to operate on, defaults to 'customer'. Selected from node UI dropdown.
• operation — Operation to perform, defaults to 'getAll'. Selected from node UI dropdown.

Output shape

Each customer record from the Pennylane API is output as a separate n8n item via auto-split.

No additional parameters (e.g., customer IDs) are required for this operation combination; the node retrieves the full list.

Examples

Example 1: A workflow builder adds the Pennylane node, sets Resource to 👤 Customer and Operation to Get All. The node calls GET /customers, receives all customers, and n8n automatically splits the response so each customer appears as a separate output item, enabling immediate use in downstream nodes like IF, Set, or Loop Over Items.

The node's displayOptions include a success-themed notice (getAllSplitNotice) explaining that each item becomes one output, ideal for n8n workflow processing.

Example 2: Rate limiting or authentication errors from Pennylane are handled by the GenericFunctions pennylaneApiRequest helper (retries with exponential back-off, specific error messages for 401/429/503 statuses).

If the API returns HTML instead of JSON, the node surfaces authentication or rate-limiting guidance.

Example 3: The operation does not consume input items' data to determine the API call; it loops over whatever input items are present (if any) and makes the same GET /customers request for each.

If no input items are connected, the node may still execute depending on n8n execution context, but typically requires a trigger to run.

Links

• n8n community nodes installation guide