Call Multi FileFeed

Call Multi FileFeed lets you invoke another FileFeed's transform pipeline as a single step inside your current Multi FileFeed (MFF). This is useful for reusing shared logic, like a standard cleaning routine or a common set of validations, across several MFFs without duplicating nodes.

Availability: GA

What it does

• Input: files or lists produced by the upstream node.
• Output: whatever files or lists the called MFF's transforms produce. The output shape depends entirely on the sub-MFF you call.
• The transform hands its input to the selected MFF, runs that MFF's transforms, and returns the result to the calling MFF so downstream nodes can continue processing.

When to use it

• You have a set of transforms — like a standard address-cleaning routine — that several MFFs should share.
• You want to keep a complex MFF readable by breaking it into smaller, named sub-MFFs.
• You are migrating logic incrementally and want to test a sub-MFF in isolation before inlining it.

How to configure it

In the MFF builder, add a Call Multi FileFeed node where you want the sub-MFF to run.

Settings

Configuration tips

• The called MFF should expect input that matches what your upstream node produces. Mismatched input types can cause the sub-MFF to fail.
• The called MFF runs its latest saved version. If the called MFF has no saved version, it runs the latest draft. Save the called MFF before re-running the calling MFF to pick up the latest edits.
• Avoid circular references: an MFF cannot call itself, directly or indirectly.

Example

Setup

A "Shared Cleanup" MFF trims whitespace and standardizes date formats. Three separate MFFs call it with Call Multi FileFeed instead of duplicating those transforms.

Result

Each calling MFF receives cleaned files back and continues with its own MFF-specific transforms.

Troubleshooting

The node fails immediately

• Confirm the selected MFF still exists and hasn't been deleted or archived.
• Check that the input type produced upstream matches what the called MFF expects.

Changes to the sub-MFF aren't reflected

• Re-run the calling MFF. The called MFF runs its latest saved version (or the latest draft if it has never been saved).

See also

• Fetch from SFTP
• Push to S3
• Fetch Salesforce Data