Setup guide
Setup is a paid implementation service between a buyer and a seller. It turns a purchased n8n workflow into a working automation inside the buyer's own environment, with credentials, fields, webhooks and tests configured properly.
FlowMarket connects both sides, displays offers, enables messaging and handles secure payment. The seller remains responsible for the setup service they sell, including scope, access handling, configuration, delivery, testing and support.
Definition
Setup is the paid work required to configure an existing workflow for the buyer's environment. It is not unlimited custom development, and it is not long-term maintenance unless the seller clearly includes it.
A reliable setup needs a clear brief, the right access, realistic test data and a written definition of what counts as successful delivery.
How it starts
Before the seller starts, both sides should agree on what will be configured, what access is needed, what test data will be used and what counts as a successful delivery.
Name the exact workflow purchased or requested, including tools, triggers and expected output.
Ask for the buyer's n8n type, tool accounts, API access method, example data and business rules.
Use limited access, avoid primary passwords, configure credentials and document what was changed.
Test the workflow with realistic data and check that each critical node behaves as expected.
Share execution results, screenshots, output examples or a short delivery note.
Explain how to use the workflow, what can be edited and when extra work or maintenance is needed.
Minimum content
The exact offer can vary by seller, but these points should be explicit for any reliable setup service.
The exact workflow, template or automation covered by the setup.
Whether setup is for n8n Cloud, self-hosted n8n, a sandbox or another environment.
The apps, APIs, databases, CRMs or services that must be connected.
How credentials will be created, shared, limited and revoked after setup.
Which fields, columns, tags, IDs, payloads or properties need to be adapted.
The sample data, test scenario and expected result used to validate setup.
Expected delivery time, working days, support hours and seller availability.
The corrections included when setup does not match the agreed scope.
Whether short setup support is included, and when maintenance becomes separate.
Scope clarity
Setup makes an existing workflow operational. Major redesign, new business logic and unrelated integrations should normally be quoted separately unless the seller clearly includes them.
If setup is blocked
Setup depends on the buyer providing the required environment, credentials, permissions and test data. If these are missing, the seller may not be able to deliver the service as planned.
Security
Setup often requires technical access. That access should be scoped to the work, documented, and removed once setup is finished unless a separate support or maintenance agreement is active.
A seller should not ask for the buyer's main password. Use safer access methods.
Prefer guest accounts, OAuth, service accounts, limited tokens or a dedicated sandbox.
When setup is delivered, the buyer should remove access that is no longer needed.
Before agreeing
FAQ
No. A buyer can purchase a template alone if they want to configure it themselves. Setup is useful when the buyer wants the creator or seller to configure it for them.
No. Setup normally means configuring an existing workflow. Custom development should be sold as a custom workflow service unless it is clearly included in the offer.
Not by default. Setup covers configuration and delivery. Monitoring, incident fixes and future API changes should be covered by a separate maintenance plan unless the seller explicitly includes them.
The buyer normally provides or creates the required accounts, permissions and credentials. The seller helps configure them inside the workflow according to the agreed scope.
A setup is successful when the agreed workflow runs in the buyer's environment, with the listed tools connected, the agreed test completed and the expected result produced.
Browse existing FlowMarket offers or request a custom setup service with clear scope, required access, delivery time, test conditions and support rules.