Free tools Windows power users keep installed
One-click scans. No signup required.
The n8n API node lets one n8n workflow manage another part of the n8n instance through the public REST API. You can create, retrieve, publish, unpublish, and delete workflows; inspect or remove executions; manage credentials; and generate a security audit. Start by confirming that your plan includes API access, create an API key under Settings > n8n API, and send that key in the X-N8N-API-KEY header. Use versioned paths such as /api/v1/workflows, then verify every workflow created through the API because a community report described a successful request that produced an apparently empty workflow.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
This guide explains the supported operation groups, setup, authentication, safe workflow design, pagination, Cloud and self-hosted differences, direct HTTP alternatives, recent API changes, and recovery steps when an operation does not behave as expected.
As an Amazon Associate I earn from qualifying purchases.
What the n8n API node actually automates
The n8n API node is an administrative automation tool. It does not primarily call an outside service from n8n; it calls n8n’s own public REST API so that a workflow can operate on workflows, executions, credentials, and selected instance functions. A scheduled workflow, deployment pipeline, or internal control workflow can therefore perform tasks that would otherwise require opening the n8n user interface.
The node exposes a documented subset of the public API as predefined operations. The operation names and parameter controls can change as n8n evolves, so use the labels shown in the version of the node installed on your instance and confirm request details in the current endpoint reference.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
| Resource or function | Operations listed in the node documentation | Typical use |
|---|---|---|
| Security | Generate a security audit | Run an on-demand review from a scheduled or supervised workflow. |
| Credentials | Create, get, delete | Provision, inspect, or remove credentials as part of controlled administration. |
| Executions | Get, delete | Inspect execution records or clean up records according to an approved retention process. |
| Workflows | Publish, unpublish, create, delete, get | Move a workflow through a lifecycle, retrieve its definition, or remove it. |
The node is not the whole API. The endpoint reference covers the broader public REST surface, while the node presents only the operations selected for its built-in integration. If the action you need is absent from the node, use an HTTP-based approach against the documented endpoint rather than assuming that a hidden node option exists.
Check your n8n edition before building
API access depends on the hosting plan. The n8n API node is listed as available on n8n Cloud Starter, Pro, and Enterprise plans and on all self-hosted editions. It is not available on the free trial. This check should happen before you design a workflow, because a missing node or unavailable API-key screen is usually an edition limitation rather than a workflow error.
| Environment | API node availability | Important qualification |
|---|---|---|
| n8n Cloud Starter | Available | Use the Cloud instance’s API base URL and key. |
| n8n Cloud Pro | Available | Use the Cloud instance’s API base URL and key. |
| n8n Cloud Enterprise | Available | Enterprise key scopes are available when configuring a key. |
| Self-hosted editions | Available | The API playground is also available on self-hosted n8n only. |
| Free trial | Not available | The node and API-key workflow cannot be assumed to work during the trial. |
Availability does not mean that every account can perform every operation. Permissions, key scopes on Enterprise, and the target instance’s configuration still control what a request can do.
Create an n8n API key
API authentication uses a key generated in the n8n settings area. Keep the key private: it grants API access to the instance according to the key’s permissions and expiration.
- Sign in to the n8n instance that the automation will manage.
- Open Settings > n8n API.
- Choose a descriptive Label so you can identify the automation later. Names such as “deployment workflow” or “nightly audit” are more useful than a generic label.
- Set an Expiration time. Prefer a lifetime that matches the automation’s operational need rather than an unnecessarily permanent key.
- If the account is on an Enterprise plan, choose the required API Scopes. The available choices are defined in n8n’s API Scopes reference; grant only the capabilities this workflow needs.
- Create the key and store it in n8n’s credential system or another approved secret store. Do not place it in a Set node value, a workflow note, a repository, or a log message.
Every authenticated request sends the key in the X-N8N-API-KEY header. A generic request has this shape:
curl -H 'X-N8N-API-KEY: $N8N_API_KEY' 'https://<your-n8n-host>/api/v1/workflows'The host in that example is a variable for your own Cloud or self-hosted address, not a universal n8n URL. Keep the path versioned. The documented examples use paths such as /api/v1/workflows; omitting the version can send a request to the wrong route or make future upgrades harder to control.
Recommended Free Tools
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Set up the n8n API node in a workflow
Exact credential-field names and some operation parameters are version-sensitive. The following sequence uses the stable concepts documented for the node without assuming an unverified UI label.
- Create or open a controlling workflow. Use a manual trigger while testing. A schedule, webhook, or deployment trigger can replace it after the request is verified.
- Add the n8n API node. Search for the node by its n8n API name rather than selecting a generic HTTP node by mistake.
- Create or select the API credential. Enter the key generated in Settings and use the credential field offered by the current node version. Do not paste the key into ordinary node parameters.
- Select an operation. Choose one of the documented actions, such as Workflows > Get or Executions > Get. The current node may group these under resource and operation selectors.
- Enter the required identifier or filters. A get, delete, publish, or unpublish action normally needs the target resource identified. Use the node’s current parameter help and the endpoint reference for the exact field and value format.
- Run a test execution. Inspect the returned item, HTTP status, and error details before connecting the result to a destructive step.
- Add a decision or approval gate for destructive actions. A delete operation should not run merely because a list returned an unexpected item. Filter, compare identifiers, and require an explicit condition.
- Activate only after verification. Test against a noncritical workflow or instance when possible, then document the key owner, expiration, operation scope, and rollback method.
The node’s predefined operations make common tasks easier than constructing raw HTTP requests, but they do not remove the need to understand the target resource. A successful HTTP response means the server accepted the request; it does not by itself prove that a workflow contains the intended nodes or that a deployment is usable.
Automate workflow lifecycle tasks
Retrieve a workflow before changing it
Use Workflows > Get to fetch the current definition before publishing, replacing, or deleting anything. Save the returned identifier and definition in a controlled location if your process needs an audit trail. Comparing the current object with the desired version helps prevent an automation from acting on a similarly named workflow.
For a deployment process, a safe sequence is:
- Request the target workflow by its identifier.
- Check that the response identifies the expected workflow and instance.
- Compare a version marker, name, or other field that your release process controls.
- Stop with an explicit error if the object does not match the expected target.
- Only then perform a publish, unpublish, update-through-supported-method, or delete action.
The node documentation lists create and lifecycle operations, but exact create payload fields should be taken from the endpoint reference for your n8n version. Do not infer a payload schema from a different release.
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 matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Create and publish a workflow
Workflows > Create can place a new workflow on an instance. A practical automation should treat creation as a two-stage transaction: create, then verify. Immediately retrieve the new workflow and inspect its nodes, connections, name, and other expected properties. If it is correct, use Publish when your release process requires publication.
A community user reported that a workflow created through the public REST API appeared empty, with no nodes visible, even though the request succeeded. The available report did not establish a resolution. Consequently, never mark a deployment successful solely because the create request returned success. A verification GET, followed by a human review for important production changes, is the safer acceptance test.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Unpublish or delete deliberately
Unpublish is appropriate when a workflow should remain stored but no longer be active in the published state. Delete is destructive. Before deletion, retrieve the object, confirm the identifier, record any required export or backup, and place the delete step behind an explicit condition. If an automation processes a list, add a second check inside the loop so a malformed or empty response cannot turn into a broad deletion.
Use execution operations for operations and cleanup
The node lists Executions > Get and Executions > Delete. A monitoring workflow can retrieve execution information for a selected workflow or incident, then route failures to an alerting or ticketing step. A retention workflow can delete execution records only after applying the organization’s retention rule.
Do not treat deletion as a substitute for diagnosing a failure. Capture the execution identifier, status, relevant error details, and timestamp before deleting a record. If your policy requires longer retention, send the approved fields to an appropriate archive before the delete request.
Manage credentials with extra safeguards
Credential operations are powerful because they affect secrets used by other workflows. The API node lists Credentials > Create, Get, and Delete. Use these operations only in a tightly controlled administrative workflow.
- Keep the API key and the credential data out of ordinary execution output.
- Limit who can edit or activate the controlling workflow.
- Use Enterprise API scopes when available to narrow what the key can do.
- Check that a credential name or identifier is unique before creating a replacement.
- Read the current credential metadata before deleting anything, and require an explicit match.
- Test a newly created credential with a harmless operation before assigning it to production workflows.
The exact fields required to create a credential vary with credential type and n8n version. Consult the current endpoint reference and node help rather than copying a payload from an unrelated example.
Generate a security audit from a workflow
The security operation listed in the node documentation generates a security audit. This can be scheduled, started after a deployment, or run as part of an incident-response workflow. Treat the result as an assessment to review, not as proof that every security concern has been eliminated. Route the output to an access-controlled destination and avoid exposing sensitive details in broad notifications.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Handle pagination when listing large result sets
Pagination is documented for large API result sets. A single request may therefore return only part of the workflows, executions, or other collection. When building a reporting or cleanup workflow:
- Read the pagination fields returned by the endpoint and node.
- Store the cursor, offset, or page value exactly as documented for that endpoint.
- Request the next page until the response indicates that no more items remain.
- Deduplicate identifiers if a long-running process can overlap with changes on the instance.
- Rate-limit or batch destructive work so a large collection does not create an uncontrolled burst.
Do not assume that every endpoint uses the same pagination parameter names. Use the endpoint-specific reference and test with a collection large enough to cross a page boundary.
Choose the node or direct HTTP calls
The built-in node and direct REST calls use the same public API but suit different jobs.
| Decision point | n8n API node | Direct HTTP request |
|---|---|---|
| Ease of setup | Predefined resources and operations are selectable in the workflow editor. | You must construct the method, URL, headers, parameters, and body yourself. |
| Coverage | Convenient for the operation groups exposed by the node. | Can reach endpoints documented by the full public API reference, including actions absent from the node. |
| Maintenance | Node updates can expose current controls, but field labels may change between releases. | You control the request explicitly and must track API-version and schema changes. |
| Hosting | Available on supported Cloud plans and self-hosted editions. | Usable from scripts, CI/CD systems, or any HTTP client that can reach the instance. |
| Governance | Uses n8n credentials and can be constrained by Enterprise key scopes. | Requires your own secret storage, request policy, and logging controls. |
| Testing tools | Test executions occur inside an n8n workflow. | The API playground is available on self-hosted n8n only; otherwise use an HTTP client or script. |
Use the node when a documented operation fits and you want visual, inspectable workflow logic. Use a direct HTTP request when the endpoint reference provides an action the node does not expose, or when an external deployment system must call n8n without running an n8n workflow.
Cloud, self-hosted, and endpoint discovery
The API examples support both self-hosted and Cloud instances, but the base host differs. Build the host from the address of the instance you administer and retain the documented version prefix in the path. Never copy a self-hosted URL into a Cloud deployment or assume that a local reverse-proxy path is identical to the public address.
The API playground for trying calls is available on self-hosted n8n only. Cloud users can test through the n8n API node, an approved HTTP client, or a script using the generated key. The endpoint reference is generated from the OpenAPI specification, making it the appropriate place to check methods, paths, request fields, response shapes, and pagination details that the node’s abbreviated controls do not show.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Recent API capabilities to account for
Instance settings in n8n 2.31
Starting with n8n 2.31, instance-level settings can be read and updated through the public REST API, beginning with the security policy. If you automate settings changes, pin your process to the API version and confirm the setting’s scope before applying it. A settings workflow should include an export or recorded previous value so an incorrect change can be reversed.
Portable .n8np packages
Workflows can be bundled into a portable .n8np package and moved between instances through the Public API or matching CLI commands. This creates an alternative to constructing a workflow definition directly in a create request. Whichever transport you use, verify the imported workflow on the destination instance and account for credentials, environment-specific values, and activation state separately.
Security and operational controls
An API key is an administrative credential, not a harmless integration token. Apply these controls:
- Least privilege: On Enterprise, select only the scopes required for the job. On other plans, separate keys by purpose and restrict access to the workflows that use them.
- Expiration: Record the expiration date and schedule key rotation before it arrives. A failed rotation should alert an owner rather than silently stopping deployments.
- Secret handling: Store keys in n8n credentials or an approved secret manager. Mask headers and values in logs.
- Change control: Treat publish, unpublish, credential, settings, and delete operations as administrative changes. Keep an execution record or external audit entry.
- Environment separation: Use different keys for development, staging, and production instances.
- Failure isolation: Add conditions, retries appropriate to the operation, and a stop path that prevents a partial result from triggering destructive follow-up steps.
Troubleshoot common failures
| Symptom | Likely explanation | What to check |
|---|---|---|
| The n8n API node is missing. | The account may be on the free trial or the node is unavailable in the current edition. | Confirm the plan and hosting type before changing workflow configuration. |
| The API-key page is unavailable. | The plan, role, or instance version may not expose the setting. | Open Settings > n8n API with an account authorized to manage keys and verify plan availability. |
| The request is unauthorized. | The key is absent, expired, mistyped, or sent under the wrong header. | Send the exact X-N8N-API-KEY header, check expiration, and regenerate the key if necessary. |
| The route is not found. | The host or versioned path is wrong. | Confirm the instance base URL and use the documented /api/v1/... path for the operation. |
| A request succeeds but the workflow is empty. | The create payload may have been accepted without the intended node definition; a community report describes this symptom. | Immediately retrieve the workflow and inspect nodes and connections. Do not publish until they are present. |
| Only some records are returned. | The collection is paginated. | Process the documented cursor, offset, or page fields until completion. |
| A field shown in a tutorial is absent. | The node UI or API schema may differ by n8n version. | Use the current node help and OpenAPI-generated endpoint reference instead of copying old labels. |
| A Cloud test cannot open the API playground. | The playground is a self-hosted-only feature. | Test with the node or an external HTTP client using the Cloud instance URL. |
Reliable automation patterns
Deployment promotion
A promotion workflow can retrieve a destination workflow, compare its identity, create or import the desired version, verify nodes and connections, and publish only after validation. Keep the create and publish actions separate so a malformed definition remains unpublished.
Nightly inventory
A scheduled workflow can page through workflow and execution records, write an inventory to an access-controlled store, and flag unexpected additions or failures. Because pagination and identifiers are explicit, the inventory can be rerun without assuming that the first response contains everything.
Credential rotation
A controlled rotation process can create a replacement credential, test it, update dependent configuration through the supported mechanism, and delete the old credential only after a successful verification. Include an expiry warning and a manual stop branch so a failed test does not remove the working credential.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Security review on change
After an approved deployment, trigger the security-audit operation and send findings to the team responsible for remediation. Restrict the destination because audit output can reveal sensitive configuration details.
Quick Recap
Pre-release checklist
- The plan is Starter, Pro, Enterprise, or a supported self-hosted edition, not the free trial.
- The API key was created under Settings > n8n API with a clear label and finite expiration.
- Enterprise scopes, where applicable, include only required capabilities.
- The key is stored as a secret and transmitted in the
X-N8N-API-KEYheader. - Every URL uses the correct instance host and a versioned path such as
/api/v1/workflows. - The operation and parameter names were checked against the current node and OpenAPI endpoint reference.
- Collection processing handles pagination.
- Create operations are followed by a GET that confirms nodes and connections.
- Delete, unpublish, credential, and settings actions have explicit checks and a recovery plan.
- Cloud users know that the API playground is self-hosted only.
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.
