The n8n API node lets one n8n workflow operate another part of the n8n platform: it can create, read, publish, unpublish and delete workflows, inspect or remove executions, manage credentials, and generate a security audit. To use it, first confirm that your plan includes the node, create an API key in Settings > n8n API, then authenticate requests with the X-N8N-API-KEY header and versioned paths such as /api/v1/workflows. This guide shows how to set it up safely, choose between the node and direct HTTP calls, and build reliable automation around it.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
What the n8n API node does
Most n8n nodes automate an outside service. The n8n API node is different: it automates n8n itself through the public REST API. A workflow can use it to perform platform-management tasks that would otherwise require opening the n8n user interface or writing a separate script.
As an Amazon Associate I earn from qualifying purchases.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe node exposes a set of documented operations, while the public REST API and its OpenAPI-based endpoint reference cover the broader API surface. The node is therefore a convenient, structured front end for common administration jobs, not a guarantee that every REST endpoint is available as a prebuilt operation.
Check plan and hosting availability first
The API node is available on n8n Cloud Starter, Pro and Enterprise plans and on all self-hosted editions. It is not available during the free trial. If you cannot find the node, check the plan or edition before troubleshooting credentials or workflow JSON.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Environment | API node | API playground | Additional governance detail |
|---|---|---|---|
| n8n Cloud Starter | Available | Not stated | Key scopes are not described as an Enterprise-only choice |
| n8n Cloud Pro | Available | Not stated | Key scopes are not described as an Enterprise-only choice |
| n8n Cloud Enterprise | Available | Not stated | When creating a key, you can choose scopes |
| Self-hosted editions | Available on all editions | Available | Enterprise scope selection depends on the edition and account |
| Free trial | Not available | Not stated | Upgrade or use a supported self-hosted edition |
Availability describes the built-in node. The public REST API can also be called directly by scripts, CI/CD systems and other HTTP clients, subject to the instance’s authentication and plan rules.
Create an n8n API key
Create the key in the n8n instance that the automation will manage. A key is tied to that instance, so a key issued by one environment should not be assumed to work against another.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Sign in to n8n and open Settings > n8n API.
- Choose a descriptive Label, such as
workflow-promotion-ciorexecution-cleanup. A label makes later rotation and revocation understandable. - Set an Expiration time. Prefer a lifetime that matches the automation’s maintenance schedule rather than an unnecessary permanent credential.
- On an Enterprise plan, select the required API Scopes. Grant only the capabilities the workflow needs; consult the API Scopes reference for the available choices.
- Save the key and copy it to a secret store. Treat it like a password: do not place it in a Set node, a log message, a shared workflow export or source control.
When a key expires, requests using it stop authenticating. Plan a replacement and update the workflow or secret store before the expiration date. If you rotate a key, test one harmless read operation before enabling destructive actions.
Authenticate requests correctly
Send the key in the X-N8N-API-KEY HTTP header. Use a versioned API path, for example /api/v1/workflows, and use the base URL of the target Cloud or self-hosted instance.
export N8N_BASE_URL='https://n8n.example'
export N8N_API_KEY='store-this-in-a-secret-manager'
curl --fail --silent --show-error
-H "X-N8N-API-KEY: $N8N_API_KEY"
"$N8N_BASE_URL/api/v1/workflows"The command illustrates the header and path format; endpoint-specific query parameters and request bodies come from the current endpoint reference. Do not infer a body schema from an unrelated operation. The API documentation is generated from an OpenAPI specification, so use that reference when the node’s fields or a direct HTTP request require details that are not shown in the node’s operation list.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Add and configure the API node in a workflow
The exact field labels can change between n8n releases. The safe configuration process is consistent:
- Open a workflow in the n8n editor and add the n8n API node.
- Choose the operation that matches the job, such as getting a workflow or deleting an execution.
- Select or create the API credential that contains the key for the target instance. Keep the credential separate from ordinary data fields.
- Provide the resource identifier and other fields requested by that operation. Use the node’s current help text and the endpoint reference for required values; do not guess parameter names.
- Run a read-only operation manually. Confirm the returned instance, workflow ID, execution ID or other identifier before connecting a write or delete step.
- Add an explicit guard, such as an IF node that checks an allowlist of IDs, before publishing, deleting or changing anything.
- Activate the workflow only after the test run shows the expected target and response.
A useful design is to keep discovery and mutation separate. One workflow can collect and review candidate IDs, while a second, manually approved workflow performs publishing or deletion.
Operations exposed by the node
The node documentation lists these operations. Names and field layouts should be checked against the version installed on your instance.
| Area | Operations listed in the documentation | Typical automation use |
|---|---|---|
| Security | Generate a security audit | Run a scheduled audit and route the result for review |
| Credentials | Create, get, delete | Provision or retire credentials under an approved policy |
| Executions | Get, delete | Inspect runs and remove selected execution records |
| Workflows | Publish, unpublish, create, delete, get | Promote, archive, inspect or provision workflows |
The list does not establish that every possible REST action has a matching node operation. If the action you need is absent, consult the endpoint reference and use an HTTP client or HTTP Request node only when the endpoint, authentication and request schema are documented for your n8n version.
Useful automation patterns
Schedule a security audit
Use a Schedule Trigger, call Generate a security audit, then send the returned findings to the review channel your team already uses. Keep the result intact so reviewers can distinguish a clean run from a failed API call. Add an error branch that alerts when the audit request itself fails; an absent report is not proof that the instance is secure.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Clean up selected executions
Start with the Get executions operation and filter the returned records using criteria approved by your retention policy. For example, an IF node can require that an execution is older than the policy threshold and is not on an exception list. Pass only approved IDs to Delete executions. Test against a single known record before allowing a loop to delete multiple records.
Large result sets require pagination. Follow the pagination fields documented for the endpoint, request one page at a time, and continue until the response indicates that no page remains. Store a checkpoint if the cleanup may exceed one execution window, so a retry does not restart destructive work blindly.
Promote a workflow between instances
A promotion workflow can read a workflow from one instance, create it on another instance, and publish it after validation:
- Use Get workflow against the source instance.
- Validate the returned name, ownership or tag and the expected node count before sending it onward.
- Use Create workflow against the destination instance with the request format documented for that release.
- Read the newly created workflow on the destination and inspect its nodes, connections and settings.
- Publish it only after the verification step succeeds.
Do not assume that a successful create response means the workflow is usable. A community report described a workflow created through the public REST API that appeared empty, with no visible nodes, even though the request succeeded. The available report does not establish a fix, so verification after creation is an essential safety step.
Provision and retire credentials
Credential automation is high impact. A controlled workflow can create a credential for an approved integration and later delete it when a project ends, but the key used to call the API must itself remain protected. Use an allowlist of credential types and names, require an approval signal for deletion, and avoid writing secret values into execution data or notifications.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Maintain a workflow catalog
Use Get workflows on a schedule, paginate through the results, and write a catalog containing non-secret metadata such as IDs, names, status and last review time. A catalog makes it easier to find unpublished or abandoned workflows without opening each project manually. Keep the catalog destination separate from the n8n API credential.
API node versus direct HTTP calls
Both approaches use the same public API and key header. The practical choice is whether you value a guided node operation or complete endpoint control.
| Decision factor | n8n API node | Direct HTTP or script |
|---|---|---|
| Ease of setup | Predefined operations and credential fields inside the editor | You must construct the URL, headers, query parameters and body |
| Coverage | Limited to the operations exposed by the installed node | Uses the broader public REST API described by the endpoint reference |
| Workflow integration | Native expressions, branching, retries and execution history | Requires a separate client, CI job or an HTTP Request node |
| Pagination | Implement the documented page loop in workflow nodes when needed | Implement the same documented pagination logic in code |
| Experimentation | Test in the editor | Self-hosted n8n includes an API playground; the playground is not available on n8n Cloud according to the documentation |
| Governance | Uses the API key attached to the node credential | Uses the API key supplied by your client or secret store |
Choose the node for repeatable jobs that fit its listed operations. Choose a direct HTTP client when you need an endpoint or field the node does not expose, or when the automation belongs in an existing deployment pipeline rather than inside n8n.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Version paths, pagination and the endpoint reference
Use versioned paths
Use paths such as /api/v1/workflows rather than an unversioned guess. Versioning makes the intended API contract explicit and helps you notice when a future version changes a request or response.
Read the generated OpenAPI reference
The endpoint reference is generated from the OpenAPI specification. Use it to confirm the HTTP method, path parameters, required fields, response shape and pagination behavior for your n8n release. This is especially important for create and delete calls, where a syntactically valid request can still target the wrong resource or omit required data.
Design for pages, not one giant response
List endpoints can return large result sets. Build a loop that requests a page, processes its records, checks the documented continuation value and then requests the next page. Add a maximum-page or maximum-record guard so a malformed continuation value cannot create an endless workflow execution.
Security and operational safeguards
- Use least privilege. On Enterprise, select only the scopes required for the job. A workflow that only reads workflows should not hold permission to delete credentials.
- Limit exposure. Store the key in n8n’s credential system or an approved secret manager. Never echo it in a Code node, notification, debug output or exported JSON.
- Separate environments. Keep development, staging and production keys and base URLs distinct. A test workflow should not be able to publish to production by accident.
- Protect destructive operations. Add ID allowlists, approval gates and a dry-run read step before delete, unpublish or credential changes.
- Plan expiration. Record the key label and expiration owner, then rotate before expiry and verify a read-only call with the replacement.
- Handle failures explicitly. Route authentication failures, validation failures and empty responses to an alert path instead of treating every nonempty HTTP response as success.
Recent API capabilities to account for
In n8n 2.31, instance-level settings can be read and updated through the public REST API, starting with the security policy. This expands API automation beyond individual workflows, so apply stricter review to any job that changes instance-wide behavior.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Workflows can also be bundled into a portable .n8np package and moved between instances through the Public API or matching CLI commands. Treat a package as a deployment artifact: validate its destination, inspect its contents after import and publish only after the same checks you would apply to a workflow created through the API.
Troubleshooting checklist
The n8n API node is missing
- Confirm that the instance is on Cloud Starter, Pro or Enterprise, or on a supported self-hosted edition.
- Confirm that you are not using the free trial, where the node is unavailable.
- Refresh the editor after a plan or edition change and check the node search again.
Authentication fails
- Check that the header name is exactly
X-N8N-API-KEY. - Verify that the key has not expired or been revoked.
- Confirm that the credential belongs to the instance in the base URL.
- On Enterprise, check that the key’s scopes include the requested operation.
The endpoint returns not found or an unexpected route
- Confirm the instance base URL and remove accidental duplicate path segments.
- Use a documented versioned path such as
/api/v1/workflows. - Check the current endpoint reference rather than copying a path from an older example.
A create call succeeds but the workflow is empty
Read the workflow back immediately and inspect its nodes and connections. Compare the request body with the schema in the endpoint reference, and keep the workflow unpublished until the contents are visible and correct. The community report documenting this symptom did not include a confirmed resolution, so verification is the reliable control.
The API playground is unavailable
The documented API playground is available on self-hosted n8n only. On n8n Cloud, test through the node, an HTTP client or your deployment pipeline using the same authenticated, versioned endpoint.
The node’s fields do not match an example
Operation-level field names can vary by n8n version. Use the help text in your installed node and the OpenAPI-generated endpoint reference as the authority. Do not paste an unverified request body into a production workflow.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A safe rollout sequence
- Confirm plan or edition availability.
- Create a labeled, expiring API key and choose Enterprise scopes when applicable.
- Test authentication with a read-only operation against the intended instance.
- Build the workflow with logging that excludes keys and secret values.
- Add pagination, retries and a bounded loop for list operations.
- Add allowlists and approval gates before writes, publishing, unpublishing or deletion.
- For workflow creation or import, read the result back and verify nodes and connections.
- Run a limited production test, then monitor failures and rotate the key on schedule.
Following this sequence keeps the n8n API node useful for administration and deployment without turning a convenient workflow step into an uncontrolled production credential.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
