Maintenance guide
Maintenance is an ongoing service between a buyer and a seller. It helps keep an n8n workflow monitored, fixed and updated after delivery, with a clear scope agreed before the recurring service starts.
FlowMarket connects both sides, displays offers, enables messaging and handles secure payment. The seller remains responsible for the maintenance service they sell, including scope, response time, delivery, support and reporting.
Definition
Maintenance is a paid agreement that defines how the seller supports a workflow once it has been delivered or installed. It is not simply being available sometimes, and it is not unlimited development.
Before a buyer pays or activates a recurring service, both sides should agree on what is included, what is excluded, response times, access rules, communication channel, reporting and stop conditions.
How it starts
A serious maintenance offer should be readable before purchase and confirmed in writing through the listing, quote or FlowMarket messaging.
Name the exact workflow or workflows covered by the maintenance plan.
Clarify monitoring, incident handling, minor fixes, API-change handling and reporting.
State what counts as extra work, such as redesign, new features or new integrations.
Explain what happens after cancellation, failed payment or non-renewal.
Minimum content
The exact offer can vary by seller, but these points should be explicit for any reliable maintenance plan.
Which workflow or workflows are covered.
Whether executions, failures, alerts or logs are watched.
What counts as an incident and how it is handled.
Expected response time, support hours, working days and time zone.
What small corrections or adjustments are included.
Whether third-party API changes are covered, and within what limits.
Where support happens: FlowMarket messages, email, calls or ticketing.
Whether incident notes, summaries or periodic reports are provided.
What happens after cancellation, non-renewal or payment failure.
Scope clarity
Maintenance protects an existing workflow. New products, major changes and unrelated integrations should normally be quoted separately unless the seller clearly includes them.
If payment stops
Maintenance is recurring. If the buyer cancels, does not renew, or payment fails, the seller is no longer expected to keep providing the maintenance work after the paid period or according to the agreed terms.
Security
Maintenance often requires technical access. That access should be scoped to the work, documented, and revoked when the service ends.
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 maintenance ends, the buyer should revoke access that was provided for the service.
Before agreeing
FAQ
No. Maintenance is optional unless a seller's offer clearly requires it for a specific service.
No. Maintenance reduces risk and gives the buyer support when something breaks, but third-party APIs, credentials, hosting and external tools can still fail.
Only if the seller clearly includes them. By default, maintenance should cover monitoring, fixes and minor updates, not major new features.
The seller may stop maintenance after the paid period or according to the agreed terms. No more monitoring, incident fixes, updates, support or reports are expected under that service.
Yes. If the seller no longer maintains the workflow, the buyer should revoke the access that was provided for maintenance.
Browse existing FlowMarket offers or request a custom workflow service with a clear maintenance scope, response time, access rules and stop conditions.