Import Check TABLE RECIPES · BETA
Two tables.
Every match explained.
Prepare columns and match records with rules you can reuse. Get the output file, unmatched rows and a trace back to both inputs. Duplicate keys block the join so you can resolve them first.
The fixed example shows two matches, one changed amount and an unmatched record on each side. No key or card required.
REUSABLE RULES
Make the result explicit.
Keys match exact strings. Both sides need unique, non-empty keys. Choose which unmatched records to retain in the recipe.
1 MB, 10,000 records and 250,000 cells across the input tables; up to 100 columns and 10,000 characters per cell. Complete reports, or an uncharged size error. No files or recipes stored.
Use your existing €9 / 100-operation pack. A completed report uses one operation even if duplicate keys or conversion errors block the output. Invalid requests and service failures are not charged.
Result
Run the fixed example to see the matches and exceptions.
Full result and row lineage
No result yet.
A repeatable step in your workflow.
Keep the recipe with your Make scenario or application. Send the next files with the same rules and a new request ID. Reuse an ID only when retrying the same inputs. The API and MCP return the same report.
This beta does not retrieve files, schedule runs, write to your CRM, evaluate formulas, perform arithmetic or make fuzzy matches. If a conversion fails, no partially transformed file is returned. Review findings before using any output.
Read the recipe reference and HTTP setup · Use the original CSV validator