Start where work actually gets stuck
Illustrative scenario: a three-person studio copies website inquiries into a project list. The owner wants “something in Make.” But the form already saves submissions in a spreadsheet. The real problem is that nobody assigns the next action. Another transfer would create a second list without making anyone responsible for responding.
Before choosing software, follow one real inquiry from arrival to reply. Record where it waits, who takes it next, and what that person needs. Automatic copying does not resolve a missing decision. Repeatedly entering known information into another app, however, may justify a connection.
Three routes for the same job
| Route | When to consider it | What to check |
|---|---|---|
| An existing app feature | The form, records, and tasks can already live in one system | Required fields, plan, teammate access, and recovery |
| A manual step with a named responsible person | Transfers are infrequent or still need judgment | Queue review, backup coverage, and missing-case detection |
| Make or n8n | Two necessary apps cannot transfer a particular field or event | Trigger, field mapping, recovery, maintenance, and total cost |
An existing or native feature performs the required step without adding another intermediary. Google Forms, for example, can save responses to a linked spreadsheet. Google also documents unlinking that destination. This does not mean the spreadsheet identifies the correct project or assigns a teammate automatically.
Check the feature against a specific record
Find the form or integration settings in your current app. Check your actual subscription, not just a marketing feature list. Transfer a harmless sample inquiry and inspect its text, contact, arrival time, and original source link. Then open it using the account of the teammate who will handle it.
Name any missing field precisely: “the project list does not show the requested service” is a useful requirement. “Connect everything” is not. Fix access problems before adding another app, which may simply pass the same problem downstream.
The subscription is only part of the cost
An existing feature may require a higher plan, middleware another subscription, and the manual route regular staff effort. Compare the same fields, people, and outcome. Use the workflow cost calculator, rather than one product’s advertised price.
When another platform becomes worthwhile
Add it when you can identify the necessary transfer, the existing route cannot cover it, and someone can maintain it. Decide where an unresolved case will be retained and who will repair it. Make documents incomplete-execution storage as a separate setting. A connected pair of apps therefore does not supply a complete recovery process.
For the studio above, first assign responsibility and review the list daily. If unnecessary copying into another necessary app remains, define that single transfer and compare Make with n8n against it.
Documentation reviewed October 1, 2026. The decision method is our synthesis; the studio and time calculation are illustrative, not customer results.