Credentials

Endpoints for credentials under /api/v1/credentials. Product UI: Secrets and Integrations and credentials.

Endpoints

List and create

GET /api/v1/credentials returns { credentials[] } with secret values masked (maskedValue). Optional oauthScopes may appear when the stored JSON contains scopes.

POST /api/v1/credentials stores an encrypted secret (AES-256-GCM). v1 always creates scope: "workspace":

The value is validated for the given type and stored encrypted — it is never returned in plaintext. Claude Code / Codex CLI session types cannot be created here (they are connected from the local AI CLI worker login flow). Returns 201 with { credential }.

Update, delete, and test

PATCH /api/v1/credentials/{id} accepts { name, type, value }; omitting value leaves the stored secret unchanged. DELETE returns { deleted: true }. Missing ids: 404.

POST /api/v1/credentials/{id}/test resolves the secret and runs a live connection check, returning { result }.

Ghost Content (ghostContentApi) and Ghost Admin (ghostAdminApi) accept distinct native raw JSON profiles with exactly adminOrigin and apiKey; see Ghost limits. Save preserves validated original material after outer whitespace trimming, sends no provider request and creates no JWT. Their explicit Test endpoint returns an unsupported result without provider HTTP or signing; saved shape does not verify identity, plan, version or privileges. Generic nonempty persistence remains unverified until execution validation.

Gotify (gotifyApi) accepts native raw JSON with url and application/client tokens; see Gotify limits. Settings validates locally after outer trimming; Save sends no provider request and leaves authentication unverified. The explicit Test helper returns unsupported without provider HTTP. Existing caller credential-read authorization still applies and can refuse Test before that result. Lower generic nonempty persistence remains unverified until execution validation.

Next steps

Hunter (hunterApi) stores an existing raw API key. Settings validates locally after outer trimming. Save sends no provider request and leaves authentication unverified; Test is unsupported and remains subject to existing credential-read authorization. See Hunter limits.

Home Assistant (homeAssistantApi) stores raw JSON with exactly apiOrigin and accessToken. Settings trims and validates locally; Save sends no provider request and remains unverified. Test is unsupported and retains existing read authorization. Generic nonempty storage can hold malformed unverified JSON. See Home Assistant limits.

Humantic AI (humanticAiApi) stores JSON containing exactly apiKey. Settings validates the original received JSON before outer trimming, including its 32,768 JavaScript-unit limit. Save sends no provider request and remains unverified; Test is unsupported and existing credential-read authorization can refuse it. Generic nonempty persistence may retain malformed unverified material. See Humantic AI limits.

Iterable uses iterableApi JSON with exactly apiKey and explicit region (us or eu). Settings enforces its received limit before trimming outer JSON whitespace; Save is unverified and sends no request, and Test is unavailable. See Iterable setup.

HighLevel uses highLevelPitApi JSON with exactly accessToken, locationId and explicit apiVersion: "2021-07-28". This sub-account PIT profile is separate from OAuth. Settings enforces the original received limit before outer trimming; Save is unverified with zero provider requests and Test is unavailable. See setup and limits.

Keap uses native keapApi with exactly accessToken in Advanced JSON, separate from OAuth. Settings applies the original received JSON limit before outer trimming. Save remains unverified with no provider request; Test connection is unavailable. See Keap setup and limits.

Invoice Ninja uses native invoiceNinjaV5Api with Advanced JSON containing exactly apiToken. Original received JSON and visible-ASCII token bounds are local validation, not vendor format verification. Save sends no provider request and remains unverified; Test is unsupported. Self-hosted, v4 and OAuth profiles are not included. See hosted v5 setup.

LinkedIn uses native linkedInAccessTokenApi with exactly accessToken in Advanced JSON. The manual existing-token profile validates original received JSON locally before outer trimming; Save sends no provider request and remains unverified, while Test and OAuth acquisition/refresh are unavailable. Historical n8n OAuth profiles are not aliases. See LinkedIn setup and limits.

Mandrill uses native mandrillTransactionalV14Api with exactly apiKey in Advanced JSON. Settings validates the original received JSON locally before outer trimming. Save sends no provider request and remains unverified; Test connection is unavailable. It does not infer live/test key status, permissions or billing and is not an alias of historical mandrillApi. See Mandrill setup.

LingvaNex uses native lingvaNexCloudV3Api with exactly apiKey and raw-key Cloud v3 authentication, separate from historical lingvaNexApi. Magento uses native magento2Api with exactly a canonical HTTPS host and existing accessToken, without minting or a modules probe. Settings validates original received JSON before trimming; both Save locally/unverified with zero provider requests and have no Test action. Token rights, expiry and merchant configuration remain unknown. See LingvaNex and Magento.

Home Assistant actions uses separate homeAssistantActionApi with apiOrigin/accessToken; Matrix uses matrixClientV3Api with homeserverUrl/accessToken; Mailcheck mailcheckApi and Mindee mindeeInvoiceApi each use apiKey; Monica monicaClassic4xApi uses apiToken; MessageBird messageBirdApi uses accessKey. Settings validates original received JSON locally before trimming; Save sends no provider request and stays unverified, Test is unavailable and generic nonempty storage may retain malformed data refused by runtime. No OAuth or historical credential alias is inferred. See the six finite profiles.

Mindee ReceiptV5 adds separate mindeeReceiptApi with exactly apiKey; InvoiceV4 retains mindeeInvoiceApi, and each operation accepts its own profile only. Monica Calls reuse monicaClassic4xApi/apiToken. MoceanV2 adds moceanApi with exactly mocean-api-key and mocean-api-secret. Save remains local/unverified and Test unavailable; no OAuth or profile substitution is inferred. Settings checks original received JSON before trimming, with32,768-unit and local visible-ASCII bounds. See the eight additions.

Mistral adds mistralCloudApi with exactly apiKey; global Graph reads add microsoftTeamsGraphV1Api with exactly accessToken. Native Teams does not accept historical microsoftTeamsOAuth2Api or generic account names. Save is local/unverified with zero HTTP and Test unavailable; no OAuth acquisition, refresh or identity/permission probe is included. Original received JSON is bounded before trimming and exact saved accounts are selected on the block. See the nine finite actions.

The workspace Teams OAuth callback saves microsoftTeamsOAuth2Api, independently of the manual native microsoftTeamsGraphV1Api account. Their token formats and native block selection remain separate.

Existing Monica Classic4.x and global Graph-v1 token profiles now also cover Activities5 and Teams WRITE9. Monica has35 finite actions; Teams has17. Save remains local/unverified0HTTP and Test unsupported. The same exact selected credential and workspace live control apply; mutations require applicable initially unchecked policies plus separate confirmation. Manual Planner ETags are operation inputs, not token fields. See the fourteen field and response contracts.

Perplexity Agent uses the exact native perplexityApi profile with JSON containing only apiKey; runtime validates original received bounds and normalizes before generic gateway expiry handling. Save is local/unverified with zero provider HTTP, Test unsupported, and generic nonempty persistence may retain malformed material refused at execution. OpenThesaurus has no credential/profile/Save/Test placeholder. See the two field, response and privacy contracts.

Outlook token reads use the separate exact microsoftOutlookGraphV1Api/accessToken account, with no historical OAuth substitution. Monica conversations6/contacts5 reuse monicaClassic4xApi/apiToken. Save remains local/unverified0providerHTTP and Test unsupported. Generic Outlook JSON Save may retain malformed shape refused at execution; received secret bounds and exact four-field normalized credentials apply before generic expiry handling. See the23 field and response contracts.

The same exact microsoftOutlookGraphV1Api/accessToken account now supports16 finite writes beside12 reads. Save remains local/unverified0providerHTTP, Test unsupported, and no OAuth acquisition/refresh or generic credential substitution is added. The selected context stays outside tool input. Saving grants no mailbox authority and does not replace unchecked applicable acknowledgments plus separate confirmation. See Outlook token writes.

urlscan requires exact native urlscanV1Api and Marketstack exact marketstackV2Api, each with only apiKey. Settings checks original received JSON before trimming; named fields serialize it, while malformed Advanced JSON cannot silently collapse through Format JSON or Use fields. Save stays local/unverified0providerHTTP, Test unsupported, and generic nonempty persistence may retain malformed material refused at execution. No OAuth issuance/refresh, identity probe or generic/historical profile substitution is provided. The prepared-account fingerprint check reads bounded stored-record identity without resolving or decrypting the secret. With database persistence, current credential and authority read failures refuse execution instead of selecting a cached connection. See account, field and verification boundaries.

npm public reads have no account

npm-public-v1 has no credential profile, OAuth, account selector, connection Save/Test or historical npmApi conversion. Native configured credential fields are rejected; this is an exact four-operation policy, not a general authentication:none exception. Generic gateway credentialRef behavior is unchanged. See the npm field, response, privacy and timing contract.

Zulip Basic and Google Books query keys

Select a saved zulipBasicV1Api account containing exactly apiOrigin, email and apiKey, or googleBooksApiKey containing only apiKey. These profiles do not convert zulipApi, googleBooksOAuth2Api or service-account credentials. Save is local and unverified; Test, OAuth acquisition and refresh are unavailable. Malformed original Advanced JSON cannot be silently repaired by Format JSON or Use fields. Generic nonempty storage can still retain material execution refuses. See the privacy, account and operation limits.

Google BigQuery and Business Profile manual accounts

Use exactly googleBigQueryManualBearerApi with only accessToken, or googleBusinessProfileManualBearerApi with exactly accessToken, accountName and locationName. The Business Profile destinations are full accounts/... and locations/... strings; they establish no ownership, grant or account/location association. Keep tokens and IDs as exact strings, with no Bearer prefix or surrounding whitespace. Save is local/unverified with zero provider requests; Test, OAuth acquisition/refresh, service-account import and historical credential conversion are unavailable. Project approval, business eligibility, scopes, expiry, access, quota and billing remain unverified. Select the matching saved account; saving grants no execution confirmation. See typed fields, whitespace, live-control precedence and limits.

Google Chat, Cloud Storage and Natural Language tokens

Use exactly googleChatManualBearerApi, googleCloudStorageManualBearerApi or googleNaturalLanguageManualBearerApi, each with only accessToken. Select the matching saved account on the block. Save is local/unverified with zero provider requests; Test, token acquisition, refresh and service-account import are unavailable. Identity, membership, rights, expiry, quotas and charges remain unverified. Saving grants no execution authority. Inputs and results may be retained. See the account and operation contracts.

Google Translate and Contacts manual tokens

Use exactly googleTranslateBearerV2Api or googleContactsManualBearerApi, each containing only accessToken. Select that exact saved account on the block. Save is local/unverified with zero provider requests; Test, acquisition, refresh and service-account import are unavailable. Rights, scopes and expiration remain unverified. Historical OAuth credentials are not converted. Saving grants no execution authority. See the account, privacy and operation limits.

Microsoft OneDrive and SharePoint manual accounts

Use exactly microsoftOneDriveManualBearerApi with accessToken and driveId, or microsoftSharePointManualBearerApi with accessToken and siteId. The selected drive or site is saved outside operation input; preserve string IDs, case and leading zeros. SharePoint uses the supported hostname,GUID,GUID profile. Save is local/unverified with zero provider requests; Test, OAuth acquisition, refresh and historical credential conversion are unavailable. Saving proves no token audience, permissions, expiry, tenant consent, ownership or execution authority. Select the exact matching account and confirm each read independently. Ordinary inputs and selected results may persist. See fields, first-page limits and supported ID profiles.

Slides and Entra manual metadata accounts

The public catalog distinguishes Google Slides · selected metadata reads (google-slides-metadata, googleSlidesManualBearerApi) from the existing Google Slides OAuth/service-account integration. Microsoft Entra ID · selected metadata reads uses microsoft-entra and microsoftEntraManualBearerApi. Each new credential contains only accessToken. Select that exact saved account on its matching block. Save is local and unverified with zero provider requests; Test is unavailable. No token acquisition, refresh, OAuth consent, service-account signing or automatic credential conversion is provided. Saving verifies neither identity, scopes, audience, permissions, expiry, quota nor execution authority.

Slides exposes presentations.getMetadata and pages.getMetadata with exact string IDs and an explicit typed metadataFields array. Entra exposes users.getMetadata, groups.getMetadata, users.firstPage and groups.firstPage. Get accepts exact GUID-shaped IDs only in this native subset, preserving case and leading zeros; Graph IDs are opaque, not universally GUIDs. Differently serialized response IDs are refused. First-page reads require numeric integer pageSize 1–100, always report inventoryComplete:false and expose only hasNext; continuation is discarded, never returned or followed.

Independent runtime confirmation remains required, without an extra acknowledgment field. The controls are WORKFLOW_LIVE_GOOGLE_SLIDES_METADATA_MANUAL_BEARER and WORKFLOW_LIVE_MICROSOFT_ENTRA_MANUAL_BEARER. An explicit workspace boolean overrides the environment; otherwise exact false disables and an absent flag enables. Personal/directory metadata, document IDs, inputs and selected results can persist in normal workflow history and downstream steps. No writes, membership changes, discovery, full slide content, media downloads or automatic follow-up is added. Account access and live provider behavior remain unverified.

See Integrations and credentials for account setup and limits, and Block reference for exact inputs and selected outputs.

Graph Security and Workspace Directory manual accounts

Use already-acquired bearer tokens without a Bearer prefix. Graph's field is Existing unverified Microsoft Graph Security access token. Directory's fields are Existing Google Workspace Directory access token and Selected Google Workspace customer ID. Directory customer selection stays outside operation input: exact 1–128 ASCII letters/digits/underscore/hyphen, preserving case and leading zeros. Raw whitespace is preserved and refused, never trimmed into a different destination. No my_customer, domain, email or URL aliases. The subset does not promise every valid Google ID.

Save the exact matching manual account locally and unverified, then select that saved account on the matching block. Save account sends zero provider HTTP requests; Test connection is unavailable. Existing credential disclosure choices remain separate from independent per-run execution confirmation. Saving grants no execution authority and adds no operation acknowledgment field. Token identity, audience, expiry, permissions, customer eligibility, quota, licensing and any charges remain unverified. Inputs, projected outputs, downstream data and run history may persist in ordinary workflow storage. No OAuth acquisition, refresh, signing, discovery, search, writes, membership changes or n8n import aliases are provided.

Directory user responses must match the saved customer. Group responses have no customer field, so successful reads do not independently verify group-customer ownership. Graph receives full upstream control profiles before discarding unselected content locally; the decoded 1 MiB body bound is not a raw-wire guarantee. See the exact Graph Security contract and Directory contract. Existing OAuth credentials and wider original n8n nodes are separate; no conversion or broad parity is implied.

Webex, SecurityScorecard and Wise manual accounts

Select that exact saved account on the matching block. Save is local and unverified with zero provider HTTP; Test is unavailable. Do not add a Bearer or Token prefix to these fields. Saving neither verifies token rights, expiry, quota, account eligibility or compatibility nor grants execution authority. Credential disclosures remain separate from independent per-run confirmation, without an extra operation acknowledgment input. No token acquisition, validation, OAuth consent, renewal or credential import conversion is provided.

Inputs and selected results may persist in ordinary workflow history and downstream steps. Full bounded upstream responses can include private fields before local projection. Webex retains only selected meeting metadata; SecurityScorecard returns company summary or bounded factor metadata and derived issue counts; Wise returns only id/type/optional currentState. The Wise origin/version is fixed to api.wise.com/2026Q4, with no legacy TransferWise v1 fallback. SecurityScorecard 403/404 errors are terminal and never enroll, create or upgrade anything.

The separate controls are WORKFLOW_LIVE_WEBEX_MEETING_MANUAL_BEARER, WORKFLOW_LIVE_SECURITYSCORECARD_READ and WORKFLOW_LIVE_WISE_PROFILE_READ. Explicit workspace booleans override environment values; otherwise only exact false disables and unset enables. Later authority checks still apply to the selected account and live permission. See Webex bounds, SecurityScorecard bounds and Wise bounds.

Travis CI and Tapfiliate manual accounts

Use Settings → Integrations to save the exact profile as a workspace credential, then select that saved account in its block. Both forms have one required password field, preserving exact visible ASCII 0x21–0x7e, 1–4096 characters, without trimming:

Advanced JSON uses exactly {"apiToken":"existing-manual-token"} for Travis CI or {"apiKey":"existing-user-key"} for Tapfiliate. Travis CI requires an existing hosted .com v3 manual token and fixes api.travis-ci.com/v3 with token authorization and Travis-API-Version: 3. Tapfiliate sends X-Api-Key to api.tapfiliate.com/1.6; its user key operates within one advertiser account and is not read-only or program-restricted. Tapfiliate rejects a matching whole-value quote pair, while allowing internal quotes.

Save and reopening send zero provider HTTP; status stays unverified and Test is unavailable. Neither profile acquires, renews, introspects or validates credentials. Existing credential disclosures remain separate from required independent per-run confirmation, without an extra acknowledgment or billing input. Saving grants no execution authority. Use workspace credentials for ordinary workflows; organization-scoped credentials are unsupported. Organization visibility alone is insufficient: execution needs direct workspace membership, organization membership and execute authority.

Full bounded private bodies enter memory before projection. Inputs, selected output, history and downstream data use ordinary workflow retention. A single GET can consume quota; rights, expiry, eligibility, free quota and applicable charges remain unverified. See account and run rules and exact block fields.

Onfleet, Storyblok and PostHog metadata accounts

These three native profiles use existing credentials. In Settings → Integrations, choose the exact provider and enter the required fields; select that saved account in the block. Advanced JSON uses exactly these keys:

{ "apiKey": "existing-key-or-token" }

The first shape applies separately to Onfleet or Storyblok. For PostHog:

{ "personalApiKey": "existing-personal-key", "region": "us", "organizationId": "11111111-1111-4111-8111-111111111111" }

Replace placeholders with existing values; the UUID is an illustrative shape. No field is trimmed. Onfleet needs an unrestricted organization API key; task-only keys are ineligible. It uses Basic authentication with the key as username and an empty password, not OAuth. Such a key may permit broader vendor access than these reads. Storyblok requires an EU public CDN v2 token for a space you may access, fixed to api.storyblok.com and published stories. Token type and location are not introspected; draft/private content, management and other regions are unsupported.

PostHog requires your own existing personal automation key without Bearer, exact lowercase us or eu without default or inference, and an exact lowercase organization UUID without padding. Region and organization remain saved destination fields, outside operation input. Existing project:read, project membership/visibility and organization policy must permit access; detail needs at least MEMBER membership. Project-restricted personal keys are unsupported for list. Do not broaden a key or bypass policy. This profile does not establish OAuth distribution eligibility.

Save and reopening send zero provider HTTP; the status remains unverified and Test is unavailable. Saving does not validate identity, permissions, eligibility or expiry, obtain/renew OAuth grants, or authorize a run. Use workspace credentials for ordinary workflows. Organization-scoped credentials are unsupported. Organization-visible workspaces still require direct workspace membership, organization membership and execute authority.

Credential disclosures remain separate from required independent per-run confirmation, without an extra acknowledgment or billing choice. Full bounded upstream private bodies—including Storyblok content and PostHog tokens/settings—enter memory before projection. Inputs, selected outputs, history and downstream data use ordinary retention. One GET attempt can consume quota; charges and rights are not guaranteed. See the account and run rules and block inputs.

Paddle Billing and Plivo existing accounts

The Paddle apiKey field is a required password. Its environment field is required text with live/sandbox suggestions, without a default. Plivo authId and authToken are both required password fields.

Paddle accepts an existing Billing key with exactly 69 characters matching pdl_(live|sdbx)_apikey_[a-z0-9]{26}_[a-zA-Z0-9]{22}_[a-zA-Z0-9]{3}, or a legacy Billing key of exactly 50 lowercase alphanumeric characters. Enter the environment explicitly even for legacy keys; the current key prefix must match it. Values are not trimmed, inferred or defaulted. Syntax does not prove product.read permission. Classic vendorId/vendorAuthCode, client tokens and automatic credential conversion are unsupported.

Plivo Auth ID is 1–128 ASCII letters or digits; Auth Token is 1–4096 visible ASCII characters. Values are exact, without trimming. Paddle Advanced JSON must be a compact single-line object without physical control characters or line breaks. This raw-format restriction does not apply to Plivo JSON whitespace. Advanced JSON uses exactly {"environment":"sandbox","apiKey":"existing-billing-key"} or {"authId":"existing-auth-id","authToken":"existing-auth-token"}; these placeholders are not usable credentials.

Saving is local and unverified, with zero provider HTTP; Test is unsupported. Saving does not authorize an SMS. Each run requires independent confirmation; there is no additional billing acknowledgment or setting.

Use an existing workspace credential and select that exact account. Organization-scoped credentials are unsupported. Execution requires direct workspace membership, organization membership and execute authority; organization visibility alone is insufficient. Credential disclosure is separate from required independent confirmation for each run.

The full bounded upstream body enters server memory before projection. Inputs, selected results, workflow configuration, history and downstream data may be retained. Rights, permissions, expiry, account eligibility, quota and charges remain unverified. Plivo logging defaults to true; sender eligibility, recipient consent, regional rules, fees and delivery are unverified. See operation fields and account and run rules.

ProfitWell Metrics and Peekalink Preview existing accounts

Both secrets preserve 1–4096 visible ASCII characters without trimming, acquisition or renewal. ProfitWell uses the token directly in Authorization: current vendor prose and endpoint examples conflict with its machine Bearer scheme. There is no Bearer inference, fallback or compatibility probe. Peekalink uses current Bearer authorization, without legacy X-API-Key fallback.

ProfitWell Advanced JSON requires a compact object with no physical control characters, line breaks or surrounding whitespace, for example {"accessToken":"existing-private-token"}. Peekalink permits JSON whitespace, for example {"apiKey":"existing-key"}. These placeholders are not usable credentials.

Use an existing workspace credential and select that exact saved account. Organization-scoped credentials are unsupported. Execution requires direct workspace membership, organization membership and execute authority; organization visibility alone is insufficient. Credential disclosure remains separate from independent confirmation of every run. Saving and reopening send zero provider HTTP, leave the account unverified and grant no execution authority; Test is unsupported.

Full bounded upstream bodies enter server memory before selected projection. Inputs, selected financial or preview results, workflow history and downstream data use ordinary retention. Rights, expiry, account eligibility, quota and charges remain unverified. These selected subsets do not provide full n8n action, field, item-loop, raw-output or error compatibility, import aliases or automatic Tool materialization.

See operation fields and account and run rules.

The catalog labels are ProfitWell · selected metrics and Peekalink. Both named secret controls are required password fields and preserve exact whitespace for validation; ProfitWell formats compact JSON, while Peekalink formats ordinary pretty JSON. Advanced raw bytes are validated before formatting.

Phantombuster existing key and optional vendor organization

Choose Phantombuster (phantombuster-agent-metadata) and an existing workspace account of type phantombusterMetadataApi. Its required apiKey is a password control with exact visible ASCII text, 1–4096 characters; do not trim it. Optional vendorOrganizationId accepts 1–128 ASCII letters, digits, underscores or hyphens. This selects the vendor organization using X-Phantombuster-Org; it grants no Plaice organization or workspace authority. Requests use endpoint-specific X-Phantombuster-Key, without old Key-1/v1 fallback.

Saving and reopening are local, send zero provider HTTP and leave the key unverified. Test is unsupported. Select that exact saved workspace account for a run; organization-stored credentials are unsupported. Execution requires direct workspace membership, organization membership and execute authority. Current-account revision and exact prepared-request binding are checked again before dispatch. Target-bound personal execution has not been tested. Credential disclosure does not replace independent confirmation of each of the five operations; there is no extra acknowledgment or billing input.

Advanced raw JSON permits JSON whitespace and is bounded to 16384 code units and UTF-8 bytes. The named-field producer emits pretty JSON; the formatter validates the original bytes before parsing and formatting. Reject unknown, duplicate or prototype keys, boxed/nonprimitive values and nonexact key whitespace. Example with synthetic values:

{
  "apiKey": "SYNTHETIC_EXISTING_KEY",
  "vendorOrganizationId": "vendor_org-42"
}

agent.launchRequest executes stored automation, potentially using saved platform credentials and causing scraping, external changes, quota use or charges. saveArgument:true can change saved launch defaults. agent.deleteRequest is destructive for the exact confirmed agentId; documented 400 missing-agent and 403 running-agent responses are failures. Each write makes one POST and returns only the LOCAL {requestedAgentId:<exact input>,httpStatus:200,outcomeVerified:false}. HTTP 200 does not prove launch, deletion, success or a container identity. The retained primary Swagger describes HTTP 200 without a write response-body schema; locally, an empty or bounded valid JSON body is fully scanned and discarded. Any failure after invocation leaves the remote outcome indeterminate. Do not automatically retry or read back; inspect Phantombuster separately before deciding what to do. Actual launch and delete were never performed during verification.

Full bounded upstream bodies, including discarded arguments, proxy passwords, storage, manifests or logs, may enter server memory before projection. Ordinary caller inputs, selected results, execution history and downstream data may be retained; this is not universal input redaction. Supported finite secret encodings are checked across the response, including ignored fields; arbitrary nested, mixed or encrypted encodings cannot all be recognized. Permissions, key acceptance, quota, account scope, human confirmation and real-provider behavior remain unverified.

See the five supported blocks.

Pushcut and SIGNL4 existing workspace secrets

Choose Pushcut with a saved workspace account of type pushcutApi, containing only {apiKey}, or SIGNL4 with signl4Api, containing only {teamSecret}. These are existing manually supplied secrets. Pushcut uses the raw API-Key header, not a secret notification-webhook URL key. SIGNL4 requires only the final opaque webhook team-secret segment, never the full URL or REST API key.

Save and reopen send zero provider HTTP and leave the account unverified. Test is unsupported, and no hidden option loader checks the account. Select the exact saved workspace account and independently confirm every operation, including metadata reads. Saving or accepting credential disclosure grants no execution authority. There is no extra acknowledgment or billing control. Direct workspace membership, organization membership and execute authority are required; organization-stored credentials are unsupported, and target-bound personal execution is untested.

The password labels are Existing unverified Pushcut API key and Existing unverified SIGNL4 team secret. Pushcut apiKey accepts 1–4096 visible ASCII characters with no leading or trailing whitespace; this is a local policy rather than a published vendor grammar. SIGNL4 teamSecret accepts 1–256 ASCII letters, digits, underscores or hyphens. Advanced raw JSON allows JSON whitespace but exactly one string pair, at most 16384 code units and UTF-8 bytes, with no unknown, duplicate or prototype keys. Named fields preserve the exact secret; there is no automatic trimming.

{ "apiKey": "SYNTHETIC_EXISTING_KEY" }

{ "teamSecret": "SYNTHETIC_TEAM_SECRET" }

Every operation makes one attempt, without automatic retries, fallback, readback, polling or returned-link fetching. Pushcut send returns an HTTP 200/202 receipt, with id and, for 202, scheduleTimestamp. SIGNL4 returns HTTP 201 with an optional nullable eventId; even {} is a valid selected result. Both envelopes keep outcomeVerified:false. A receipt proves neither delivery nor action execution, scheduling, alert creation, closure, acknowledgement or affected count. Resolve uses the original external correlation ID (externalId, sent as X-S4-ExternalID), never the returned eventId, and can affect multiple alerts. After invocation, a failure leaves the remote outcome indeterminate; inspect the provider separately before deciding whether to repeat a request.

For a SIGNL4 attachment, first produce a persisted file in the current workspace and pass its file descriptor under the selected Binary Property. Only PNG, JPG, JPEG, BMP, GIF, MP3 and WAV are supported, with a local 1 MiB limit checked before reading or copying. The file must still be ready, with matching size and SHA256 before and after the bounded read. Arbitrary bytes, URLs, local paths, filenames and MIME types are not accepted. Signature checks validate local magic/MIME, not full media decoding.

A standalone workflow pauses at that same SIGNL4 node after resolving the current file. Open its attachment confirmation, inspect the exact account ID, binary property, format, size and SHA256, then choose Approve attachment or Reject attachment. The approval expires after five minutes. Only the original actor can decide that exact request; changed accounts, changed files, stale decisions and replayed approvals are refused. The current file, account and execution permission are checked again after approval, together with live and cancellation state. The ordinary manual-run confirmation cannot authorize an upstream file whose digest is not yet known. Approval details omit secrets, private tokens and file content; normal file retention still applies.

Standalone placement includes the selected branch of a condition. Attachments in loop bodies, parallel branches, nested composite descendants, sub-workflows and single-step runs are unsupported and fail before preparation, approval callback or provider HTTP. No success marker or earlier approval bypasses this restriction; continuation for those placements remains future work. Ordinary Agent and human approvals keep their existing behavior.

Full bounded private provider responses enter server memory before scanning and selected-output projection. Ordinary inputs, selected results, execution history, downstream data and workspace files may be retained; there is no universal input redaction. Finite known secret encodings are checked, without a guarantee for arbitrary mixed, nested or encrypted encodings. Provider permissions, routing, quota, costs, delivery, resolve affected count and actual human/provider behavior remain unverified. Pushcut configured actions can invoke shortcuts, web requests, online actions and other systems; dynamic content requires Pro, without an upgrade or billing-consent control. SIGNL4 routing can incur SMS, voice or escalation charges.

See all five block contracts.

seven and MSG91 existing workspace keys

Choose seven with native sms77Api, containing exactly {apiKey}, or MSG91 (existing template SMS) with msg91Api, containing exactly {authkey}. The password fields are Existing unverified seven API key and Existing unverified MSG91 authkey. Supply your existing key manually. Named fields, Advanced: edit JSON and Format JSON validate locally, send zero provider HTTP and leave the account unverified. Test is unsupported; there is no OAuth flow, key loader or hidden account/template discovery.

{ "apiKey": "SYNTHETIC_EXISTING_SEVEN_KEY" }

{ "authkey": "SYNTHETIC_EXISTING_MSG91_KEY" }

Both native secret values use a local grammar of 1–256 visible ASCII characters without spaces, controls or automatic trimming. Raw JSON allows JSON whitespace but exactly the one native string pair: no duplicate, unknown or prototype keys. The local raw JSON bound is 16384 code units and UTF-8 bytes. These are local restrictions, not published key-length guarantees.

Select the exact current saved workspace account. Saving a credential or reviewing its disclosure grants no execution authority. Each of the three operations needs independent confirmation and one attempt, even with outer maxTries:3; there is no automatic retry, fallback, polling or readback. Current direct workspace membership, organization membership, execute authority, account revision and prepared identity are checked, together with live and cancellation state before dispatch. Organization-stored credentials are unsupported; target-bound personal execution is untested. There is no extra acknowledgment, billing or consent checkbox.

seven sends its raw key in X-Api-Key to the fixed https://gateway.seven.io/api/sms or /api/voice POST form, with Accept: application/json. MSG91 sends raw authkey in the header of a JSON POST to https://control.msg91.com/api/v5/flow. MSG91 requires explicit migration from the original free-form sender/to/message action to an existing approved template_id and a strict JSON recipient array with exact case-sensitive variable names. There is no automatic conversion, legacy fallback, template creation or discovery. Current compatibility of the old sendhttp.php endpoint is unknown; no deprecation or removal is asserted.

Message content, numbers, variables and sender data go to the provider and recipients and may consume quota or incur charges. seven contact/group entries can fan out beyond the submitted count; SMS encoding and segments affect costs. Tracking can shorten links; seven requires a configured custom tracking domain. Voice sender/caller-ID availability is unverified. Existing account webhooks and recipient keypress events may still operate at seven even though this integration does not implement DTMF callbacks or call control.

Accepted receipts keep outcomeVerified:false; they do not guarantee delivery, costs or template approval. seven string 100 is acceptance only; 101 can mean partial acceptance. Any failure after invocation leaves an uncertain remote outcome: inspect the provider separately before deciding to repeat. Full bounded private responses enter memory before projection; ordinary inputs, selected receipts, execution history and downstream data can be retained. Finite known-secret scanning is not universal redaction. Live key acceptance, account rights, costs, delivery and independent human confirmation remain unverified.

See the three operations and exact controls.

YOURLS installation credentials and public QuickChart

YOURLS uses an existing yourlsApi workspace account with exactly two native fields:

{ "signature": "YOUR_EXISTING_SIGNATURE", "url": "https://links.example.org/tools" }

Enter the signature in Existing YOURLS signature (unverified) and the installation base in Public HTTPS installation URL. Include an installation subdirectory when needed; omit /yourls-api.php from this field. The installation must use public DNS and HTTPS port 443. Direct API paths, HTTP/private installations, literal IPs, query strings, fragments and URL credentials are refused. There is no OAuth, automatic installation discovery or guarantee for custom plugins or authentication. Exact text is preserved; do not rely on trimming.

Named fields, Advanced: edit JSON and Format JSON only edit local credential material. Save and reopen send zero provider HTTP requests, remain unverified and offer no Test. Choose the exact current workspace account before running. Save does not grant execution authority: current direct workspace and organization membership, execute permission, account revision, HMAC material and prepared-object identity are checked for dispatch, along with live/cancel state. Organization-stored credentials are unsupported. WORKFLOW_LIVE_YOURLS controls this provider through the existing workspace/environment live policy.

QuickChart is public: authentication:none, credentials:[]. Do not create a fake API key, manual account or Connect account entry. Its public card says Public render · no account required and Independent confirmation for every render. Public access still requires current workspace and organization authority and a signed, independently confirmed render. WORKFLOW_LIVE_QUICKCHART controls execution. Saving a YOURLS account is separate from consenting to any YOURLS action or public chart disclosure.

Each shorten, expand, stats and render invocation requires independent confirmation and makes one attempt even with outer maxTries3. There is no automatic retry, redirect, fallback, polling or readback. Full bounded responses enter memory before selected projection; ordinary inputs, selected outputs, run history, downstream data and chart files may be retained. Known secret encodings are checked, without a claim to detect arbitrary encodings. A failure after invocation leaves the provider or local file outcome uncertain; inspect independently before deciding to repeat. Local PostgreSQL tests cover current workspace/organization authority and revocation using synthetic guarded HTTP responses. QuickChart file storage in those tests is an in-memory fixture. Real provider requests, DNS/TLS, MinIO/S3, ClamAV, independent human approval and hosted Review remain unverified.

Vero and Vonage native manual credentials

Save an existing Vero Track token as veroApi, with exactly authToken, or an existing Vonage SMS account as vonageApi, with exactly apiKey and apiSecret. These are strict JSON objects, not generic header credentials, OAuth grants, or tokens acquired by Confluye.

{ "authToken": "YOUR_EXISTING_VERO_TRACK_TOKEN" }

{ "apiKey": "YOUR_EXISTING_VONAGE_KEY", "apiSecret": "YOUR_EXISTING_VONAGE_SECRET" }

The named password fields, Advanced: edit JSON, and Format JSON share local validation. Save makes zero provider HTTP requests and leaves authentication unverified; Test is unsupported. The local credential limit is 16 KiB. Missing/extra fields, duplicate or unsafe prototype keys, malformed JSON, and invalid field types are refused rather than repaired. Whitespace is not silently trimmed. No new acknowledgment or billing-consent field exists. Select the exact saved workspace account on the operation. Organization-stored credentials are unsupported; organization membership alone does not supply direct workspace membership. Saving an account grants no execute permission and does not consent to a run.

Vero offers eight actions: create/update, alias, unsubscribe, resubscribe, delete, addTags, removeTags and event track. Alias can merge identities, deletion permanently removes properties and activities, subscriptions are global, and tracked events may create users or trigger campaigns. Vonage offers one SMS send with text, Unicode or literal binary hex plus UDH. Binary SMS is not a workspace-file attachment. SMS fees, segments, sender eligibility and recipient permissions remain account/provider concerns. See the exact fields, defaults, JSON/UI modes and supported/refused options in the block reference.

Vero explicitly migrates the original ambiguous body/form helper to JSON requests with auth_token query authentication on fixed https://api.getvero.com/api/v2. Event data/extras are objects, not JSON strings; redundant top-level event email is omitted. Tags are JSON arrays retaining comma splitting, spaces and empty items. Vonage explicitly migrates original form api_key/api_secret to HTTP Basic on fixed https://rest.nexmo.com/sms/json. There is no legacy fallback or substitution of Messages/Verify APIs.

Every action requires independent confirmation of its exact input/account, including any Vonage callback. Current principal, direct workspace AND current organization membership, execute permission, selected credential revision, live setting, workflow/run identity and cancellation are checked around asynchronous work. The transport checks again after its DNS await before initiating HTTP. These checks do not make the database and socket atomic. WORKFLOW_LIVE_VERO and WORKFLOW_LIVE_VONAGE separately govern live execution.

A Vonage callback requests a vendor outbound delivery-receipt flow. Its strict public-HTTPS hostname syntax and 100-character local limit do not verify endpoint ownership or control vendor DNS, sockets, redirects or delivery. Confluye adds no callback receiver, polling or receipt proof. Existing vendor account webhook configuration may also affect delivery reports.

Each invocation makes one attempt even with outer maxTries3; no retry, redirect, readback, polling or extra credential probe occurs. outcomeVerified:false is an unverified API receipt, not proof of a changed profile, campaign effect or delivered SMS. Any failure after invocation leaves the effect uncertain: investigate before deciding to repeat. Full bounded responses enter memory before selected projection; ordinary inputs, selected outputs, history and downstream retention remain. Local PostgreSQL authority cases used synthetic HTTP and confirmation. Real provider behavior, DNS/TLS, independent human consent, hosted Review and Vero/Vonage production-browser behavior remain unverified.

UpLead and OneSimpleAPI: existing accounts and confirmed utilities

UpLead enriches company and person records. OneSimpleAPI provides ten utility definitions: nine support requests and Instagram is explicitly unavailable. These are selected native integrations, not full n8n node, item-loop, credential-import, error-mode or live-provider parity. The original ordinary and Tool resource/operation aliases identify these definitions; they do not import saved credentials or certify all original options.

Choose a manually acquired provider account, then save and select the exact account for the workflow workspace. UpLead uses upleadApi with only apiKey, sent as raw Authorization, never an added Bearer prefix. OneSimpleAPI uses oneSimpleApi with only apiToken, sent as query token with output=json. A provider's individually acquired account is distinct from the application's personal storage scope. Personal accounts can execute through an exact saved-account binding owned by the current actor, with current workspace and organization permissions; real-provider and Review behavior remains unverified. Organization-stored credentials are unsupported. An organization workspace still requires current workspace and organization authority.

Named password fields, Advanced: edit JSON and Format JSON validate locally. Save sends zero provider requests, leaves authentication unverified and grants no execution authority. Test is unavailable; there is no OAuth flow, imported credential-name fallback, extra acknowledgment checkbox or billing control. Never paste account secrets into operation fields or URLs.

Independently confirm every invocation, including metered GET lookups. Review the exact operation, selected account and complete input. Current actor, workspace/organization membership, execute permission, account revision, live preference, run/workflow/version and cancellation are checked again after awaited work and at the guarded transport boundary after provider DNS. These checks do not create an atomic database-to-socket guarantee. Each invocation makes at most one attempt even when workflow maxTries=3 requests retries. A failure after invocation leaves an uncertain outcome; inspect it before manually repeating. outcomeVerified:false means there is no independent verification of the effect, not a retry instruction or a success certificate.

Inputs and selected results can remain in ordinary run history and downstream steps. Full bounded responses, including later-discarded fields, are received and scanned for known secret material before projection; this is not universal secret detection. JSON numeric lexemes are preserved as decimal strings, avoiding JavaScript rounding. Local 10-second/256-KiB and parser/read limits do not guarantee vendor, wire, allocation or operating-system bounds. Account validity, quotas, costs, current provider contracts, hosted Review flows and human confirmation remain unverified.

Save and reopen examples

Use the named password field or Advanced JSON with exactly {"apiKey":"YOUR_EXISTING_KEY"} for UpLead, or {"apiToken":"YOUR_EXISTING_TOKEN"} for OneSimpleAPI. Format only formats valid JSON locally. Save/reopen keeps the chosen account; select it explicitly for the workflow. These examples are placeholders, not operational credentials. Do not interpret an unverified saved account as a tested connection. A separate account is needed only when you intend to use that provider, not to view these reference pages.

URL disclosure and unavailable modes

PDF, screenshot, SEO, image metadata and URL expansion ask OneSimpleAPI to retrieve the exact approved public HTTPS link. The local syntax policy excludes credentials, fragments, IP literals, private/local names, non-HTTPS and nonstandard ports. Confirmation approves the exact input and current account/run authority before transport; the application does not probe the requested URL, establish target ownership, or control the vendor's DNS, sockets, redirects or remote rendering. No remote-safety guarantee follows from local URL validation. Returned links are metadata and are never followed or downloaded here.

PDF, screenshot and QR require download:false. download:true refuses before HTTP: there is no link substituted as a successful binary download and no workspace file. Instagram also refuses before HTTP because its current contract is unknown; a cached documentation 404 does not prove removal. Original QR Small/Medium/Large and PNG/SVG casing and image raw=true are retained but current vendor acceptance/semantics remain unknown. Screenshot fullpage explicitly maps to documented full=yes/no. Only the listed original options are accepted; current vendor features such as PDF background/HTML, QR colors or other output formats are not added implicitly.

LoneScale existing keys and public PostBin access

LoneScale uses native lonescaleApi (lowercase s) with exactly apiKey. Explicitly resave original loneScaleApi; there is no generic alias or fallback. Requests send x-api-key only to public-api.lonescale.com. The original overlapping Authorization/X-API-KEY intent is replaced explicitly: current endpoint security schemas specify x-api-key, although overview prose mentions Authorization. Save, reopen, named fields, Advanced JSON and Format send zero provider HTTP and leave the account unverified. Test, OAuth, credential discovery and key generation are unavailable. Select the exact saved account for the workflow workspace.

PostBin has authentication none and credentials:[]. Do not create or select a saved account, key, credential form, Test connection or OAuth flow. Its public bin/request IDs establish neither ownership nor privacy; use only bins and data you are authorized to access.

Every action, including reads and list options, needs independent confirmation of its exact input. Each action has one attempt even with imported maxTries:3. Successful and handled-failure receipts keep outcomeVerified:false; a failed write after invocation may already have changed the provider. Investigate uncertainty before repeating. Error routing does not turn failure into success, retry or compensation. Inputs, selected outputs, run history and downstream data use ordinary retention. Stored PostBin headers, body and IP can reveal personal data.

Current actor, workspace AND organization membership, execute permission, selected account revision where applicable, live run and cancellation are checked again around asynchronous work. This does not provide an atomic database/socket guarantee. Workspace accounts and explicitly selected personal native accounts resolve by exact credential ID and credential family. A personal account must belong to the authenticated run actor in the workflow workspace, with current workspace AND organization permission; its display name grants no authority and cannot select another account. Organization-stored credentials are unsupported. Missing or changed persisted run actors refuse before dispatch. A personally acquired provider key is distinct from its application storage scope. Local and synthetic tests do not prove real provider acceptance, organization persistence, independent human consent or Review behavior. No full n8n parity or durable continuation is claimed.

Stackby, Dropcontact and Oura accounts

Save an existing Stackby key as stackbyApi or a Dropcontact key as dropcontactApi, with exactly {"apiKey":"YOUR_EXISTING_KEY"}. Stackby uses the API Beta profile at https://stackby.com/api/betav1/ with api-key; other Stackby profiles are separate contracts and are not tried as fallbacks. Dropcontact uses https://api.dropcontact.com/v1/enrich/all with X-Access-Token; original .io/batch requests require this explicit migration.

Oura uses the new ouraOAuthAccessToken family with exactly {"authType":"oauth_access_token","accessToken":"YOUR_EXISTING_OAUTH_ACCESS_TOKEN"}. Supply an existing OAuth access token yourself. Retired Personal Access Tokens and original ouraApi credentials are unsupported; resaving opaque bytes does not establish token type, expiry or consent. Profile reads require personal; daily scores require daily. These are required grants, not verified consent or scope metadata. OAuth acquisition, refresh, introspection and callbacks are unavailable. Stackby and Dropcontact retain only their selected ordinary and Tool operation aliases. Oura is a separate manual-token counterpart with no n8n import aliases, including Tool aliases; migrate its inputs and account explicitly.

Use named fields or Advanced JSON; Format validates and formats locally. Save and reopen send zero provider requests and leave authentication unverified. Test connection is unavailable. Select the exact saved account for this workflow: workspace accounts or a personal account owned by the current actor can be used. Current workspace and organization permissions still apply; organization-stored accounts are unsupported. A queued run needs its original persisted actor, and changing an account, actor, workflow version or permission can invalidate an earlier approval.

Confirm the exact input independently for every physical request, including reads, later pages and status checks. Each request has one attempt even with imported maxTries:3. outcomeVerified:false remains explicit after success or a handled failure; a failed write may already have changed the provider. Investigate uncertainty before repeating. Inputs, selected results, ordinary history and downstream steps may retain data. Local and simulated checks do not establish real provider compatibility, token grants or an authenticated human decision.

Zammad, Wekan, Quickbase and Salesmate accounts

Select the exact saved account and matching credential family in the workflow. Workspace accounts and personal accounts owned by the current actor are eligible; organization-stored accounts are unsupported. Current workspace and organization execution permissions still apply. Saving does not authorize a request or verify token identity, provider rights or consent. Named fields, Advanced JSON and Format validate the strict local shape; unknown, duplicate or invalid fields are refused without silently repairing the input. Save and reopen send no provider request and leave authentication unverified. Test connection, automatic login and OAuth acquisition or refresh are unavailable for these profiles.

Zammad: explicit Basic or Token mode

Use zammadNativeBasicApi for Basic operations:

{
  "mode": "basicAuth",
  "baseUrl": "https://support.example.com",
  "username": "YOUR_EXISTING_USERNAME",
  "password": "YOUR_EXISTING_PASSWORD"
}

Use zammadNativeTokenApi for Token operations:

{ "mode": "tokenAuth", "baseUrl": "https://support.example.com", "accessToken": "YOUR_EXISTING_TOKEN" }

Choose the corresponding basicAuth.<action> or tokenAuth.<action> operation: 25 logical actions become 50 mode-qualified choices. Use the public HTTPS installation root or supported path prefix. Token mode uses Zammad's Token token= authorization. OAuth Bearer and original zammadBasicAuthApi or zammadTokenAuthApi credentials require explicit migration; no family or server fallback is tried. No n8n import aliases are declared.

Use names where a field asks for names: organization and decimal organizationId are mutually exclusive. Create needs group/organization name, user firstname and lastname, or ticket title, group, customer and article. Nested fields JSON must follow the selected resource shape; empty updates and unsafe or duplicate custom field names are refused. Supply the selected installation's custom-field names manually.

Lists, user/field options and article lists request one explicit page: page defaults to 1, perPage to 50, maximum 100. Every later page or option read needs a separate confirmation; nextPageCandidate is unverified and complete:false does not promise an exhaustive result. Migrate Return All or larger imported limits manually. Ticket creation returns its POST response without an article readback; confirm article.list separately. Article upload and attachment download use actual owned workspace files, at most 256 KiB, with current ownership, scope, ready scan state and integrity checks. Download requires ticket/article/attachment IDs, file name and MIME type. A URL is not a file and is never followed implicitly.

Wekan: existing Bearer token and selected user

Save wekanExistingBearerApi with exactly:

{
  "accountOrigin": "https://boards.example.com",
  "token": "YOUR_EXISTING_BEARER_TOKEN",
  "userId": "YOUR_EXISTING_USER_ID"
}

Use the public HTTPS installation origin or supported path prefix and supply the original opaque userId yourself. Declaring a user ID does not prove token ownership. Original wekanApi username/password credentials need explicit migration. The selected static contract targets Wekan v12.57; installed-server capability and permissions remain unverified.

There are 35 choices: 24 ordinary actions, three explicitly named runtimeChecklist actions and eight independent options reads. Only the 24 ordinary actions declare ordinary Wekan aliases; Tool aliases, triggers and attachment operations are unavailable. Each options read needs separate confirmation, and listing users may require server administrator rights.

Board owner and card/comment create author must match the selected user. Board role overrides and later card-author changes are refused. Use opaque IDs, not routes or encoded separators. For card.getAll, provide the list or swimlane ID selected by fromObject. Collections return one response, locally limited to 1–200 records, default 100; returnAll still means this bounded response, completeness is unknown and nextPage is null. There is no cursor or hidden pagination. Explicit false, zero, empty text and omission remain distinct locally. Card dates support null/empty clearing and members/assignees support empty arrays, but the server may ignore falsy updates, filter inactive members or truncate an updated card title to 1,000 characters.

Quickbase: US realm and explicit field IDs

Save quickbaseApi with exactly:

{ "authType": "user_token", "hostname": "your-realm.quickbase.com", "userToken": "YOUR_EXISTING_USER_TOKEN" }

hostname is the exact US realm hostname, without scheme or path. Requests use fixed https://api.quickbase.com/v1; EU/custom origins are unavailable. Resave original QuickBaseApi credentials explicitly. Ten ordinary actions retain ordinary and Tool aliases; getTableFields and getUniqueTableFields are two separate first-class discovery actions without aliases.

Supply table and field IDs manually. Runtime requirements still apply even when the shared form marks a field optional: a table request needs tableId, and record writes need the selected fields/items. Record writes require options.useFieldIDs:true; Update also requires simple:false and explicit Record ID field 3 matching updateKey. Hidden field discovery followed by a write and multiple physical request units are unavailable. Discover fields in a separate approved action, then configure IDs. Create, Update and Upsert share the vendor insert/update endpoint and may insert or update.

A batch has 1–10 original items, sharing item 0 table/options and per-item columns; in explicit-ID mode every item key is sent, regardless of columns. Keep itemParameters and itemBinary cardinality/order aligned. Missing or ambiguous labels/IDs and collisions refuse rather than inventing values. Each physical request, including reads and discovery, needs its own signed exact-request Human Task approval by the original actor. Review method, URL, realm, query, complete body and input indexes in the preview, at most 48 KiB. The initial path permits one physical request. Generic Run or single-step acknowledgment cannot replace this approval.

Reads return one bounded page, up to 100 records; Return All is still one page. Advance skip manually after reviewing incomplete/stalled/nextCandidate metadata; there is no snapshot or exhaustive-result guarantee. Raw envelopes remain available and JSON numeric lexemes stay exact strings; HTTP 207 line errors can mean a partial result. Downloads decode at most 1 MiB of actual bytes into owned workspace files with scan, size and SHA256 checks; returned URLs are not fetched as files.

Salesmate: existing v4 tenant token and flat CRUD fields

Save salesmateV4AccessToken with exactly:

{
  "profile": "salesmate-v4-access-token",
  "tenantOrigin": "https://your-tenant.salesmate.io",
  "accessToken": "YOUR_EXISTING_V4_ACCESS_TOKEN"
}

Use the exact lowercase HTTPS tenant origin without trailing slash, path, port, credentials, query or fragment. Central/reserved hosts, legacy salesmateApi/sessionToken and v1/v2 endpoints require explicit migration; no fallback is tried. The durable runtime with persisted authority is required; memory-only execution cannot authorize these requests.

Twelve actions create, get, update or delete one activity, company or deal. No n8n import aliases are declared. GetAll/search, custom fields, activity dueDate, bulk IDs, hidden loaders and the old Get projection are unavailable. Get requires rawData:true; create/update default to rawData:false. Get/update/delete IDs are positive decimal text, up to 20 digits. owner, primaryContact and primaryCompany use the declared numeric controls. A provider owner ID grants no app authority.

Updates require all mandatory creation fields: activity title, owner, type; company name, owner; deal title, owner, primaryContact, current pipeline/stage names, status (Open, Close or Lost) and uppercase three-letter currency. Supply pipeline/stage names manually. Migrate the original Billing State/Country collision into separate billingState and billingCountry; overwritten values cannot be reconstructed. Explicit false and zero remain supported where declared.

Author dealValue as decimal text, including expressions returning text: at most 18 total digits and nine fractional digits, optional minus sign, no plus or exponent. Preserve digits, scale, zero and negative zero. Empty text is invalid; omission remains omitted. Migrate imported numeric workflow values explicitly; already-rounded IEEE754 digits cannot be recovered. For example, use the string "123456789.123456789" without converting through Number.

Every action, including Get, requires its own durable exact-request Human Task decision by the original persisted actor. Generic Run approval and provider owner IDs are insufficient. Input preview is bounded to 24 KiB, the signed payload to 32 KiB, and approval expires after 15 minutes. Account, configuration or authority changes can invalidate it sooner. CRM writes may invite/notify people, trigger account automations and consume quota or credits. Delete is destructive; the activity soft-delete request choice does not guarantee recovery. Returned provider JSON retains numeric lexemes as strings; links remain data, without file transfer or implicit fetches.

Confirm each request and inspect uncertain effects

All four profiles require independent confirmation and current account, original actor, workspace and organization authority, workflow/configuration revision and live-run/cancellation checks. Each invocation has one attempt even when workflow retries are enabled. No automatic retry, polling, readback or compensation verifies a change. outcomeVerified:false leaves effects unverified after HTTP success; inspect uncertain changes before intentionally repeating them. Inputs, full bounded provider data, selected results and ordinary history/downstream data may persist. Saving an account or accepting a confirmation does not prove real-provider compatibility, permissions, scanning or delivery. These selected counterparts do not establish complete n8n action, field, authentication, import or runtime parity.

MISP accounts and exact requests

Save an existing MISP account as mispApi with exactly:

{ "apiBaseUrl": "https://misp.example.org/security/misp", "apiKey": "YOUR_EXISTING_RAW_API_KEY" }

Use the public HTTPS installation URL, including its exact path prefix, and an existing raw API key. Save and reopen are local and leave authentication unverified. Test connection, OAuth and automatic key acquisition are unavailable. Select the exact workspace account or a personal account owned by the run actor. Current workspace and organization execution permissions apply; organization-stored accounts are unsupported.

The 44 choices cover attributes, events, event tags, feeds, galaxies, notice lists, objects, organisations, tags, users and warning lists. Ordinary MISP and MISP Tool imports identify these covered operations; they do not establish general n8n Tool runtime compatibility. Supply IDs manually as positive decimal text with at most 18 digits. UUIDs and larger IDs require an explicit migration. Additional Fields and Update Fields accept only the declared keys; updates must contain a supported change.

For attribute, event and object search, leave Use Json off and fill Value plus optional Additional Fields. To use Json Output, turn Use Json on and clear Value and Additional Fields. JSON accepts the finite search fields value, category, deleted, searchall, tags, type, published, page, limit and returnFormat:"json"; it is not an arbitrary request body. Explicit false values remain false. GetAll returns one bounded response, with a local limit of 1–1,000 (default 50). Return All does not guarantee completeness or request another page. There are no hidden option lookups, retries or readbacks.

The original user.invited_by, organisation.usercount, organisation.created_by_email and feed-creation additionalFields.json effects are unsupported and refused. Feed update rules use their declared finite JSON shape. Insecure TLS, binary workflows and triggers are unavailable. Original source versions and the selected current API contract differ; installed-instance permissions and provider compatibility remain unverified.

Every read and write pauses for a separate exact-request Human Task assigned to the original run actor. Review the selected account, method, URL, complete body and described effect. Approval expires after 15 minutes and can become invalid sooner if the account, workflow, run, input or permissions change. The preview is limited to 24 KiB and its signed payload to 32 KiB. Another Member or Owner cannot approve on the original actor's behalf. Durable workflow execution and Human Tasks must be enabled.

Publishing an event may queue publication and fan out to other systems. Creating a user may email credentials and create an API key. Deletion can remove provider data. Each confirmed request has one attempt even when workflow retries are enabled. outcomeVerified:false remains explicit: a receipt does not independently verify the change, queued publication or delivery. After an uncertain failure, inspect the provider before intentionally repeating the request. Inputs and selected provider data may remain in run history and downstream steps; credential-like response fields are excluded, but ordinary content can still contain sensitive data.

SeaTable accounts and staged requests

Save an existing account as seaTableApi. For example:

{
  "profile": "seatable-staged-v2",
  "kind": "api-token",
  "environment": "selfHosted",
  "domain": "https://tables.example.org/team",
  "baseUuid": "11111111-1111-4111-8111-111111111111",
  "providerWorkspaceId": 42,
  "permission": "write",
  "token": "YOUR_EXISTING_TOKEN"
}

Choose cloudHosted with exactly https://cloud.seatable.io, or selfHosted with the exact public HTTPS installation and optional subpath. Enter the selected base UUID, SeaTable workspace ID and read or write permission explicitly. Save/reopen validate locally and leave authentication and permissions unverified. Test, OAuth and automatic refresh are unavailable. A base-token additionally needs an explicit future expiresAt in ISO UTC, within three days. API tokens must omit that field. Never use decoded JWT claims as proof of a grant.

The sixteen actions cover row creation, deletion, retrieval, listing, locking, search, unlocking and updates; base snapshots, metadata and collaborators; adding, listing and removing links; temporary download capabilities and asset upload. Supply existing table/column names and exact 22-character row IDs manually. Columns Ui accepts {"columnValues":[{"columnName":"Enabled","columnValue":false},{"columnName":"Count","columnValue":0},{"columnName":"Title","columnValue":""}]}. These values retain their types when saved. Options accepts only each action's declared keys. Listing/search use an explicit start and a limit of 1–1,000; link lists allow 1–100. Each returns one bounded response, without automatic pages or readbacks.

Every physical stage pauses for a separate signed Human Task assigned to the original run actor, expiring after 15 minutes. Stages can include token issuance, metadata/collaborator reads, the selected operation, file capability issuance, upload and attachment. Review the account, base, method, destination, body and request digest. Current workspace and organization authority, selected account, workflow, input and run must still match. Another Member or Owner cannot approve for the actor. Durable workflow execution, Human Tasks and the SeaTable execution switch must be enabled. API-token exchange explicitly requests a three-day grant; only the selected server's matching response can establish the local grant.

Uploads require an actual owned workspace file with matching content, revision and completed clean scan. Review replacement/append options. An upload can finish before its row attachment is approved; canceling later does not remove the uploaded asset. Temporary download capabilities can disclose file access and are not automatically fetched. Each confirmed stage makes one attempt, including when workflow retries are enabled. An uncertain attempt is not replayed. Inspect the provider before intentionally repeating it; outcomeVerified:false does not verify persistence or delivery. Inputs and selected results can remain in workflow history.

Only ordinary n8n-nodes-base.seaTable imports with explicit typeVersion:2 use this mapping. V1, versionless imports, Tool aliases and triggers need separate migration. Real provider authentication, binary/scan behavior and matching-revision Review walkthroughs remain unverified.

Nextcloud accounts, files and exact requests

Select Basic (nextCloudApi) or an existing OAuth token (nextCloudOAuth2Api) explicitly. Basic uses exactly:

{
  "authentication": "accessToken",
  "accountBaseUrl": "https://cloud.example.org/nextcloud",
  "user": "alice",
  "revision": "1",
  "password": "EXISTING_APP_PASSWORD"
}

OAuth uses the same exact HTTPS installation, username and revision with authentication: "oAuth2", token and a future expiresAt in Unix milliseconds; omit password. Saving and reopening remain local and unverified. Test, login, discovery and refresh are unavailable. Native requests currently require a publicly reachable IPv4 HTTPS installation; localhost and private networks are refused. An optional raw webDavUrl must match this account's supported DAV route exactly.

The 17 ordinary choices cover file copy/delete/download/move/share/upload, folder copy/create/delete/list/move/share, and user create/delete/get/list/update. Supply paths and user IDs manually. Paths begin with /; an empty folder-list path selects the root. Copy and move can overwrite; folder deletion is recursive. Shares can expose data or send mail, and user creation can send invitation or reset mail. Keep only fields for the selected operation: share types use the corresponding recipient; public-link passwords are unavailable on other share types. User lists return one bounded response. Return All does not traverse pages or prove completeness; leave Limit empty when it is enabled.

Each physical request requires a signed Human Task for the original run actor, expiring in 15 minutes, with the exact selected account, destination, method, body and workflow inputs. Current workspace and organization permissions must still pass. Another Member or Owner cannot decide for the actor. Durable execution, Human Tasks and the Nextcloud execution switch must be enabled. One claimed attempt is allowed even when node retries are enabled; inspect uncertain provider effects before deliberately repeating them.

Text uploads preserve an explicit empty body. Binary uploads require an owned Workspace File from a supported upstream binding; downloads are persisted through Workspace Files and its configured scanner. File ownership, readiness, bytes, MIME, hash and full revision must remain current through confirmation and OUTPUT. A direct Nextcloud download can feed an upload; arbitrary other-provider binary outputs are unsupported. A scan-state result does not establish the malware protection of a deployment that uses a test scanner. Large text previews show UTF-8 size and hash; the complete value remains bound to the signed request.

Ordinary n8n-nodes-base.nextCloud mappings cover these operations; this does not establish Tool compatibility or full n8n item, error and output parity. Results remain outcomeVerified: false, with bounded response completeness unknown. Actual provider authentication, installed-version behavior, production file scanning and matching-revision Review remain unverified.

Rundeck API 59 accounts and jobs

Use an existing token with the explicit rundeckApi59 family:

{
  "profile": "rundeck-api59-token",
  "apiBaseUrl": "https://rundeck.example.org/automation",
  "token": "EXISTING_API59_TOKEN"
}

Save the exact public HTTPS installation, including an optional subpath, on port 443. Save and reopen remain local and unverified; Test, login, discovery, version detection and refresh are unavailable. Legacy rundeckApi, API 14, insecure TLS and shell argString settings require explicit migration. The installed server's API 59 support and token rights remain unverified.

Choose job.execute or job.getMetadata and supply the exact Job ID manually. Supported IDs use ASCII letters, digits, underscores and hyphens. Execute Arguments retain the original arguments.arguments collection of unique text name/value rows, including empty, Unicode and "0" values. They become JSON options rather than a shell string. An empty or omitted Filter uses the job/server defaults and can select many remote nodes. A job can run commands, affect infrastructure, notify other systems or incur costs.

Both metadata reads and execution need a separate signed 15-minute Human Task decided by the original run actor. The selected account, exact request, workflow, input, run and current workspace and organization authority must still match. Another Member or Owner cannot approve for that actor. Durable execution, Human Tasks and the Rundeck execution switch must be enabled. Each task permits one physical attempt; retries, polling, output fetch, abort requests and returned-link following are unavailable. Before publishing OUTPUT, the workflow checks the current permissions, approved request and recorded result again. A changed approval or an uncertain result stops OUTPUT. An execution receipt is not job completion. Inspect an uncertain remote effect before deliberately repeating it.

Ordinary version-1 n8n-nodes-base.rundeck imports identify these two operations with an explicit API 59 migration notice. Unknown versions and Tool aliases remain unsupported. Results retain outcomeVerified: false; actual provider acceptance, native sockets and matching-revision Review remain unverified. Request and response bounds are local application policy, not vendor limits.

Rocket.Chat messages and existing accounts

Save an existing account with the rocketchatRestV1Api family:

{
  "profile": "rocketchat-rest-v1-token",
  "domain": "https://chat.example.org/team",
  "userId": "existing-user-id",
  "authKey": "existing-auth-key"
}

Use the exact public HTTPS installation and optional subpath on port 443. Save and reopen are local and unverified. Test, login, discovery, OAuth and refresh are unavailable. Legacy rocketchatApi accounts require an explicit resave with this profile. Saving does not establish the installed server version or message permissions.

The ordinary version-1 n8n-nodes-base.rocketchat node supports chat.postMessage: one channel or room ID, text, Options and attachments. Channel arrays, Tool and Trigger nodes, missing or unknown versions, threads, uploads and arbitrary custom fields are unsupported. Options keep alias, avatar and emoji. Alias and avatar require the server's message impersonation permission. parseUrls defaults visibly to false; attachment and avatar links may still cause Rocket.Chat servers or clients to fetch remote content.

Choose named attachment fields or JSON Parameters. Named fields preserve supported empty strings, false and 0, including nested fields.fieldsValues. JSON Parameters accepts the supported snake_case attachment array. Switching modes in the editor clears the inactive draft; raw or imported inactive fields are refused. At least nonempty text or a supported nonempty attachment is required. The original node declared messageLink but checked messageLinks during execution. Using named messageLink therefore requires explicit messageLinkMigrationAcknowledged: true to map it to message_link; this correction changes the original execution behavior.

Each message needs a signed 15-minute Human Task decided by the original run actor. Review the selected account, resolved fields, destination and exact request before approving. Current workspace and organization permissions, account, workflow, input, run and node must still match. Another Member or Owner cannot approve for that actor. Durable execution, Human Tasks and the Rocket.Chat execution switch must be enabled. Posting may notify users and disclose message data. Each approval allows one physical attempt; automatic retries, redirects, follow-up reads and returned-link navigation are unavailable. Inspect an uncertain remote effect before deliberately repeating it.

The result keeps the bounded complete success: true response, including the message ID and room ID, with outcomeVerified: false. A response is not proof of message delivery. The validated response is saved as a completed physical attempt before the final OUTPUT authority check. Inputs and responses may persist in history. Actual provider acceptance, native sockets, installed-version compatibility and matching-revision Review remain unverified. Request, response and approval bounds are local application policy, not vendor limits.

Elasticsearch REST v8 documents and indices

Select the explicit elasticsearchRestV8Basic account family and enter an existing Basic account:

{
  "profile": "elasticsearch-rest-v8-basic",
  "baseUrl": "https://elastic.example.org/search",
  "username": "EXISTING_USERNAME",
  "password": "EXISTING_PASSWORD"
}

Use the exact public HTTPS installation on port 443, including an optional subpath. This profile currently requires printable ASCII Basic account fields and conservative installation paths; these are application restrictions. Saving and reopening remain local and unverified. Test, discovery, version detection, login, refresh, OAuth, API keys and TLS bypass are unavailable. Legacy elasticsearchApi accounts require explicit migration; saving does not establish the installed version or its read, write or delete permissions.

Five document operations are available: document.get, document.index, document.update, document.delete and document.searchPage. Supply one literal Index ID and, where required, Document ID. Index with a Document ID creates or replaces that document; without one, the server assigns an ID. Server defaults may create an index or run ingest processing. Update merges a partial document and can return noop; Delete removes one document. These operations can disclose data, consume resources and incur costs.

Select parameter schema 2, acknowledge the migration, and keep Simple disabled. Ordinary version-1 n8n imports require this explicit migration to raw response namespaces; source fields cannot overwrite response identity. Missing or unknown versions and Tool aliases remain unsupported. Fields to Send retains imported text values; named controls also accept explicit JSON values such as false and 0. Quote those values when text is intended. Auto Map requires an explicit input object and supports Inputs to Ignore. Inactive fields and unsupported nondefault options are refused by name; remove or repair them before running.

Search Page returns one bounded page with a default limit of 50 and a maximum of 100. Its query accepts only match_all, term or match; source include/exclude filters are supported. Partial search results and timed-out or failed-shard responses are refused. Raw hit metadata and total relation remain available; this is not an all-results export. Bulk, arbitrary query DSL, scripts, upsert, aliases or multiple target syntax, cross-cluster targets, PIT, pagination, refresh and pipelines are outside this implemented subset. A literal name can resolve to an alias on the server; Save does not discover its target, and a returned index identity mismatch is refused.

Each physical read or write needs its own signed 15-minute Human Task approved by the original run actor. The selected account, exact request, workflow, run, input, version, live switch and current workspace and organization authority must still match. Another Member or Owner cannot approve for that actor. One physical attempt is allowed, including when node retries are configured. A complete response is recorded before OUTPUT, which checks current authority and the exact stored result again. An uncertain result is not retried or checked with a hidden follow-up request; inspect remote effects before deliberately repeating it.

All results retain outcomeVerified: false. Successful local simulation does not establish provider acceptance, native DNS/TLS sockets, installed server behavior, real account permissions or matching-revision Review behavior. Request, response, time and structural bounds are application policy, not Elasticsearch vendor limits.

Index operations

Four index operations use the same account and explicit schema-2 migration:

Create, Delete and Get require one literal Index ID. Wildcards, _all, multiple targets, cross-cluster syntax and path expressions are refused. A literal name can still resolve to an alias on the server; saving does not discover its target.

Index Get All defaults to 50 returned namespaces and allows at most 100. The complete response must fit the local 2 MiB budget and pass validation before slicing. The result keeps the selected raw namespaces and coverage.examined, returned, truncated and limit; allResultsComplete and remoteLimitApplied remain false. A short or empty result does not establish a complete inventory. Returned names may include data streams.

Index Create accepts the original empty aliases, mappings and settings defaults and the original default timeout, shard-wait and include_type_name values only as omitted controls. Index Get likewise accepts its original default additional fields only as omitted controls. Server defaults apply and may differ from those original values. Nondefault or unknown fields are refused by name; aliases, mappings, settings and query options are not transmitted. Delete and Get All accept no additional-field or option entries.

False, missing or malformed acknowledgements leave the remote outcome uncertain. Every index read or write still requires the original actor's separately signed request, current workspace and organization authority, one physical attempt and a checked stored result before OUTPUT. An uncertain outcome never triggers an automatic retry, readback or compensating request. Results retain outcomeVerified: false; local simulation does not verify installed-server permissions or remote effects.

ServiceNow incident requests

The ordinary version-1 n8n-nodes-base.serviceNow integration supports five incident operations with explicit Basic authentication and parameter schema 2. Acknowledge migration and keep Simple disabled. Other resources, attachments, OAuth, Tool/Trigger aliases and missing or unknown versions remain unsupported.

Save an existing serviceNowTableV2Basic account using named fields or Advanced JSON:

{
  "profile": "servicenow-table-v2-basic",
  "baseUrl": "https://example.service-now.com",
  "username": "EXISTING_USERNAME",
  "password": "EXISTING_PASSWORD"
}

Use an exact public HTTPS service-now.com tenant origin on port 443, with one subdomain label and no path. Save and reopen are local, make zero provider requests and leave authentication unverified. Test, login, discovery and OAuth are unavailable. Legacy Basic accounts require explicit migration and reselection; saving does not establish tenant version, roles or ACL permissions.

IDs require exactly 32 lowercase hexadecimal characters. Short description is nonempty and limited locally to 160 UTF-8 bytes; Description allows an explicit empty string and at most 4096 characters. Impact and Urgency accept integers 1–3. Unknown and inactive fields are refused by name. Read options allow distinct sys_id, number, short_description, description, impact, urgency and active projections and must include sys_id; display values false, true or all and Exclude reference link are optional. Keep boolean false distinct from an omitted field.

Writes may trigger business rules, notifications and downstream workflows. Lists retain unknown completeness even when short or empty: server limits and ACL filtering do not establish a complete inventory. Raw incident text and responses may persist in run history or reach downstream AI.

Each physical read or write requires its own signed 15-minute Human Task decided by the original run actor. The exact saved account, request, workflow, run, input, version, live switch and current workspace and organization permissions must still match. Another Member or Owner cannot approve for that actor. Durable Human Tasks and the ServiceNow execution switch must be enabled. One physical attempt is allowed, even with node retries; an uncertain outcome is never retried or checked by a hidden readback. Final OUTPUT rechecks authority and the stored result. Results keep outcomeVerified: false. Local simulated transport tests do not verify a real tenant, native sockets or matching-revision Review behavior. Bounds are application policy, not vendor limits.

Gong call reads

The ordinary version-1 n8n-nodes-base.gong integration supports call Get and one-page List through explicit schema-2 migration. Transcript is a separate native read, with its own approval; selecting transcript inside an imported Get does not cause a hidden request. Acknowledge the raw-response migration and select the matching saved account. Tool aliases, unknown versions, automatic cursors, media retrieval, users and OAuth are outside this implemented subset.

Save an existing gongRestV2Basic account with Access Key and Access Key Secret:

{
  "profile": "gong-rest-v2-basic",
  "baseUrl": "https://api.gong.io",
  "accessKey": "EXISTING_ACCESS_KEY",
  "accessKeySecret": "EXISTING_ACCESS_KEY_SECRET"
}

This profile supports only the explicitly selected https://api.gong.io origin on port 443. It does not discover the customer's region, tenant, plan, scopes, key expiry or trusted-IP policy. Legacy gongApi and OAuth accounts need explicit migration and reselection. Save and reopen are local and unverified, with zero provider requests; Test, discovery, login and refresh are unavailable.

Use exact decimal ID strings of 1–20 digits, preserving leading zeros; numeric IDs and automatic locator searches are refused. List filters allow at most five distinct Call IDs or Primary user IDs. Times use UTC seconds, for example 2026-10-21T10:00:00Z, with From before To. Get supports Include fields for parties, topics, brief, public comments, highlights, key points, call outcome, outline, structure and trackers; List supports parties and topics. Named and JSON controls preserve explicit false. Unsupported fields are refused rather than silently dropped.

All three POST requests are reads. The complete bounded raw page can contain participants, public comments, analysis or transcripts, including records beyond the local selected-item limit. Those raw namespaces may persist or reach downstream AI; a local limit is not a server-side privacy limit or a complete export. The local response budget is 1 MiB, with a 30-second transport bound; these are application restrictions.

Each read requires the original actor's separately signed 15-minute Human Task, the exact selected account and request, and current workspace and organization authority. Durable Human Tasks and the Gong execution switch must be enabled. One physical attempt is allowed, including with node retries. Settlement and final OUTPUT authenticate the stored response and receipt; an uncertain read is not retried, refreshed or followed by a hidden request. Results keep outcomeVerified: false. Provider acceptance, installed permissions, native sockets and matching-revision Review remain unverified.

Okta user requests

The ordinary version-1 n8n-nodes-base.okta integration supports five user operations through explicit parameter schema 2 and manual SSWS authentication. Acknowledge migration and select the matching saved account. OAuth, unknown versions, Tool/Trigger aliases, password changes, lifecycle operations and custom profile attributes are outside this implemented subset.

Save an existing oktaSswsUsersV1 account using named fields or Advanced JSON:

{ "profile": "okta-ssws-manual-v1", "origin": "https://example.okta.com", "accessToken": "EXISTING_SSWS_TOKEN" }

Use the exact public HTTPS tenant origin on port 443, without a trailing slash, path, query or fragment. Save and reopen are local and leave authentication unverified, with zero provider requests. Test, login, OAuth, discovery and refresh are unavailable. Legacy accounts require explicit migration and reselection; saving does not establish token permissions or tenant policies.

Manual user IDs start with 00u and use the supported ASCII form; me, login lookup and locator searches are refused. Profile controls support the 31 named standard fields, including Postal address and Zip code. Required First name and Last name retain the API's explicit null option. Null, empty text and omitted fields remain distinct where supported. Duplicate create fields, unknown attributes and expressions are refused. A Link header is untrusted data: the application never follows it automatically. A short page is not a complete inventory.

Raw user profiles may persist in run history or reach downstream AI. Each physical request requires the original actor's separately signed 15-minute Human Task, the exact selected account and request, and current workspace and organization permissions. Another Member or Owner cannot approve for that actor. Durable Human Tasks and the Okta execution switch must be enabled. There is one physical attempt, including with node retries; uncertain outcomes do not cause a hidden readback or a second delete. Final OUTPUT authenticates the stored response and receipt and rechecks authority. Results keep outcomeVerified: false. The local response budget is 1 MiB with a 30-second transport bound. Simulated tests do not verify a real tenant, provider permissions, native sockets or matching-revision Review behavior.

Unleashed sales orders and stock

The ordinary version-1 n8n-nodes-base.unleashedSoftware integration supports one sales-order page, one product's stock and one stock page through explicit parameter schema 2. Acknowledge migration and select the matching company account. Automatic pagination, writes, unknown versions, Tool/Trigger aliases and unsupported filter values are outside this implemented subset.

Save an existing unleashedHmacCompanyV1 account using named fields or Advanced JSON:

{
  "profile": "unleashed-hmac-sha256-query-manual-v1",
  "apiId": "EXISTING_API_ID",
  "apiKey": "EXISTING_API_KEY",
  "clientType": "confluye/local"
}

The origin is fixed to https://api.unleashedsoftware.com on port 443. Client type uses two lowercase letter, digit or hyphen segments separated by /, with at most 64 characters. The server signs the exact outgoing query with the company's API key. Save and reopen are local and unverified, with zero provider requests; Test, discovery, login, OAuth and refresh are unavailable. Saving does not verify company access, subscription or permissions.

Pages default to 1 and allow 1–1,000,000; limits default to 100 and allow 1–100. These are local restrictions. Keep Return all disabled. Sales filters include Customer ID GUID lists, Customer code, End date, Modified since, Order number, Order status and Start date. An Order number cannot be combined with other filters because the provider overrides them. Status supports Backordered, Completed, Deleted, Parked and Placed; omitting it does not include deleted orders automatically.

Stock filters include As-at date, Is assembled, Modified since, Product ID GUID lists, Warehouse code and Warehouse name. Explicit false is preserved. Order by supports only the empty default until a closed column contract is available. GUID lists preserve order and duplicates and allow up to 50 entries. Dates require real YYYY-MM-DD values; imported date-time truncation is refused. Raw .NET date representations remain raw, and a missing stock record does not establish zero stock.

Customer, order, stock and cost data may persist or reach downstream AI. Each read requires the original actor's separately signed 15-minute Human Task, the exact company account and request, and current workspace and organization authority. Durable Human Tasks and the Unleashed execution switch must be enabled. One physical attempt is allowed, including with node retries; there is no automatic next-page, count, retry or readback request. Settlement and final OUTPUT authenticate the stored response and receipt. Results keep outcomeVerified: false. The local response budget is 1 MiB with a 30-second transport bound. Provider acceptance, native sockets, company permissions and matching-revision Review remain unverified.

AWS SQS and Lambda requests

AWS SQS supports one sqs.sendMessage request; AWS Lambda supports one lambda.invoke request. Ordinary version-1 imports require explicit parameter schema 2 and migration acknowledgement. These selected actions do not provide complete AWS credential, region, binary or node parity.

Save an existing awsSqsManualSigV4V1 or awsLambdaManualSigV4V1 account using named fields or Advanced JSON. Use the matching profile, aws-sqs-manual-sigv4-v1 or aws-lambda-manual-sigv4-v1, partition aws, a supported region, the declared 12-digit AWS account ID, Access key ID and Secret access key. Choose manual-static, or manual-temporary with an existing Session token and explicit UTC expiresAt. Temporary credentials must remain valid beyond the 30-second request budget plus a 60-second safety margin; replace and approve them again when necessary. The declared account is an input restriction, not a verified AWS identity.

Save and reopen send zero provider requests and leave authentication unverified. There is no connection Test, sign-in, STS, role assumption, system credential chain or refresh. The fixed endpoint map includes 34 commercial regions per service. GovCloud, China, isolated partitions, custom, FIPS and dual-stack endpoints are unsupported; the map does not promise every current AWS region.

SQS supports the selected string and canonical decimal number attributes, preserves omitted delay versus zero and validates returned body/attribute MD5 values. FIFO requires explicit group and deduplication IDs and refuses per-message delay, including zero. Binary attributes are refused. Lambda does not accept an empty payload, binary results, logs or client context. Function versions, aliases and $LATEST can change without a configuration read. Messages and invocations may incur charges.

Every request needs the original actor's separately signed 15-minute approval, exact saved account and request, and current workspace and organization authority. Durable Human Tasks and the service execution switch must be enabled. SigV4 date and signature are generated at physical dispatch; approval binds the stable request and saved account revision. There is one physical attempt, with no automatic resend or readback after an uncertain result. Settlement and final OUTPUT check the authenticated stored response receipt. outcomeVerified: false does not establish downstream completion.

Business inputs and bounded JSON responses can persist in workflow history and reach downstream AI. Local limits are 32 KiB per request, 1 MiB per response and 30 seconds; these are application restrictions, not AWS limits. Local simulated tests do not establish actual AWS permissions, endpoint acceptance, native sockets or matching-revision Review behavior.

ServiceNow fixed-table ID lookups

Alongside the five incident actions, ServiceNow supports six first-page ID lookups using the same serviceNowTableV2Basic account and explicit schema-2 migration:

Explicitly enable lookupIdProjectionAcknowledged. This migrates the original Get all action to a restricted first page of sys_id values only. The limit is 1–50, default 50, with offset zero, display values disabled and reference links excluded. There is no custom query, arbitrary table, count request or automatic pagination. Empty and short pages do not establish a complete inventory. IDs can still disclose organizational structure and are retained under ordinary history and downstream-data rules.

Only HTTP 200 JSON with the exact result envelope and rows containing one lowercase 32-hex sys_id is accepted. Extra fields and display data are refused before public output. Each lookup requires the original actor's signed approval, current workspace and organization authority and one physical claim. Aborted or uncertain lookup requests settle without automatic replay; inspect the provider separately before deciding to repeat. Attachments, arbitrary table-record actions, user actions and OAuth are outside this subset. These six lookups have local simulated coverage; real provider permissions, native sockets and matching-revision Review remain unverified.

Twist text and JSON actions

The ordinary version-1 Twist integration supports 22 selected text/JSON actions through explicit parameter schema 2 and migration acknowledgement:

Save a twistManualBearerV1 account using named fields or Advanced JSON:

{ "profile": "twist-manual-bearer-v1", "accessToken": "EXISTING_MANUAL_TOKEN" }

This is a partial manual-token authentication profile. The captured official documentation provides testing tokens and requires OAuth for production public integrations. Original OAuth credentials do not migrate automatically. Saving and reopening are local and unverified, with zero provider requests; Test, sign-in, discovery, OAuth acquisition and refresh are unavailable. The endpoint is fixed to https://api.twist.com/api/v3 on port 443. Saving does not establish token identity, workspace membership or permissions.

Use exact parent/workspace/recipient IDs and literal text or structured values. Expressions are unsupported. Supported controls preserve omitted fields, empty text, false and zero where permitted. Timestamps require explicit Unix-second integers; timezone-dependent date conversion is not reproduced. Channel Update requires a nonempty Name. Temporary IDs must be negative; an imported default of zero requires repair. Original uppercase ordering requires lowercase asc or desc, and the deprecated is_starred filter requires an explicit current boolean. Conversation-list additional fields must be moved to native Filters. Conversation Create retains the original workspace ID although the current endpoint documentation does not list it; provider acceptance remains unverified.

Lists require singlePageRawAcknowledged: true; keep Return all disabled. Limits default to 50 and allow 1–500. Channel List receives and examines the complete bounded server array before local slicing; the local limit does not prevent other received records from entering raw history. Other lists make one bounded request. No list proves complete history or follows another page. Comment Get requires explicitly choosing the documented object or original comment-wrapper response shape. Raw HTTP bytes and the native data projection remain separately available; bodyless 200/204 responses and outcomeVerified: false do not prove an external effect.

Creating, editing, deleting, archiving or unarchiving content can change access or notify people. Exact recipients and parent IDs matter; raw user/message data can persist in history or reach downstream AI. Every read and write requires the original actor's separately signed 15-minute approval, the exact saved account and request, and current workspace and organization authority. Durable Human Tasks and the Twist execution switch must be enabled. One physical attempt is allowed, with no automatic retry, reconnect, cursor following or hidden readback after uncertainty. Final OUTPUT validates the signed stored response receipt and current authority.

Attachments and binary input for comment, conversation-message and thread Create/Update are unavailable. Nonempty binary references and attachment arrays are refused; no URL is fetched as a substitute. Action-button links remain provider payloads and are not fetched by this integration. Local limits are 64 KiB request, 1 MiB response and 30 seconds, not provider limits. Local simulated checks do not verify production OAuth, provider DNS/TLS/HTTP, actual encrypted database Save/reopen, the full persisted original-actor approval flow, human MFA or matching-revision Review.

SyncroMSP REST: explicit migration and one approved request

SyncroMSP supports 20 ordinary actions: create, delete, get, update and one-page list for contacts, customers and tickets, plus create, delete, get, mute and one-page list for RMM alerts. Select an existing syncromspBearerRestV1 account with profile syncromsp-bearer-manual-v1, a lower-case ASCII tenant label and an existing bearer token. The destination is fixed to https://tenant.syncromsp.com/api/v1 for that label. Saving and reopening the account is local and unverified; it sends no provider request. Test, sign-in, OAuth, token refresh and automatic discovery are unavailable. Authentication, tenant identity, permissions and provider acceptance still need verification.

Original numeric n8n node version 1 imports preserve the original parameters for repair. They require manual schema-2 conversion, a separately selected supported account, wireMigrationAcknowledged:true and the account's queryAuthMigrationAcknowledged:true: the original query API key is not silently reused as a bearer token. Tool and Trigger identities and other node versions are unavailable. Expressions and unsupported address-array writes remain visible for explicit repair and cannot execute as supported fields.

Review the exact native field names. Customer name and address aliases use their explicit wire names; ticket fields retain explicit empty, null, false and zero values where the schema permits them. An omitted invoice-CC field stays omitted, while an explicit empty list clears it. Updates require at least one selected field. For example, an explicitly migrated customer update can preserve these distinct values:

{
  "parameterSchemaVersion": 2,
  "wireMigrationAcknowledged": true,
  "id": 17,
  "fields": {
    "notes": "",
    "notification_email": null,
    "get_sms": false,
    "invoice_cc_emails": []
  }
}

RMM mute additionally requires muteQueryMigrationAcknowledged:true; it sends the duration in the documented query location rather than the original request body. The retained flat RMM-create body and ticket asset_id/ticket_type fields differ from current documentation; their live compatibility remains unverified. No alternate request is sent automatically to resolve those differences.

Lists require singlePageAcknowledged:true, default to a local limit of 25 and allow at most 100 returned items. The bounded raw page is retained before local slicing; examined and returned counts do not establish completeness. returnAll:true, cursor/Link following and hidden readback are unavailable. Local limits are 32 KiB per request, 1 MiB per response and 30 seconds per invocation. These are application limits, not provider guarantees; IPv6-only destinations are unsupported.

Every read and write needs the original run actor's separate exact-request confirmation and current workspace and organization authority. Approval expires after 15 minutes and is tied to the selected account, workflow, inputs and request. Changing the saved account requires new consent. Contact, customer, ticket and alert data can remain in execution history or reach downstream AI. Review the destination, record IDs, literal body and applicable changes before confirming. One physical attempt is allowed; ambiguous results are not retried automatically. Bodyless HTTP 200/204 and returned IDs do not verify the remote effect; results retain outcomeVerified:false.

Local controls, encryption, import round trips and the production gateway have been exercised with simulated storage and provider transport. Matching Review walkthroughs, current composed database durability, native provider sockets, real authentication/effects and AI-provider interpretation are not established by those local checks.

Taiga: manual token and explicit field migration

Taiga supports create, delete, get, update and one-page list for epics, issues, tasks and user stories. Select taigaBearerManualV1 with profile taiga-bearer-manual-v1, an exact public HTTPS origin and an existing accessToken. Named fields and Advanced JSON use the same encrypted account format. Saving and reopening are local and unverified. The original username/password login requires explicit migration and account reselection; no login, refresh, credential Test or option discovery occurs.

Original ordinary imports retain their type, version, parameters and credential references for repair. Native requests require parameterSchemaVersion:2 and migrationAcknowledged:true. Tool and Trigger identities are separate. Enter IDs manually. Updates require the current record version and manualVersionAcknowledged:true; version 0 is valid and no version lookup runs. Selected assigned_to or milestone null values clear the field where supported, while omission leaves it unchanged. False, empty descriptions or blocked notes and empty tag lists retain their distinct values. Corrected filter names, comma-separated query tags and hash-prefixed epic colors need explicit migration. Legacy user-story type additionally needs unverifiedLegacyTypeAcknowledged:true; live support remains unverified.

Lists need singlePageRawAcknowledged:true, default to a local limit of 50 and allow at most 100 selected items. The bounded raw page remains available; completeness is unknown. Return all, automatic continuation and following server next URLs are unavailable. Local limits are 64 KiB per request, 1 MiB per response and 30 seconds per invocation; these are application limits rather than provider guarantees.

Twake: historical n8n plugin message

Twake supports the ordinary message.send action through twakePluginWorkspaceKeyV1, using profile twake-plugin-workspace-key-v1 and an existing workspaceKey. The fixed destination is https://plugins.twake.app/plugins/n8n/actions/message/save. Basic, JWT and Twake Server accounts are separate unsupported modes. Saving is local and unverified; the historical plugin's current availability, permissions, response status and wrapper have not been verified with a live account.

Enter the channel ID and formatted content, with explicit schema-2 migration. The request sets object.channel_id, object.content.formatted and object.hidden_data.allow_delete:"everyone". Nonempty sender name or icon overrides are forwarded; empty overrides are omitted. An icon URL is forwarded as data and never fetched locally. One native invocation produces one request and one result, explicitly replacing the original multiple-input last-result behavior.

Both providers require the original run actor's separate exact-request confirmation, valid for 15 minutes, plus current workspace and organization authority. Changing the saved account, ciphertext, workflow, inputs or request requires fresh consent. Raw descriptions, messages and personal data can remain in history or reach downstream AI; remote changes can notify recipients or incur costs. One physical attempt is allowed. Ambiguous results are not automatically resent or read back. A response, returned ID or bodyless deletion does not verify the remote effect; outcomeVerified remains false.

The result envelope retains the bounded raw UTF-8 body, digest and item counts. Contract checks require Taiga create 201, delete 204 with no body, other Taiga responses 200 and Twake send 200; these expectations are not live-provider acceptance evidence. Invalid encoding, leading BOM, duplicate JSON keys, oversized bodies and reflected account secrets are refused. Local storage, request, approval and runtime tests use simulated database facts and provider transport. Current composed PostgreSQL durability for these providers, native sockets, real authentication/effects, AI interpretation and matching Review walkthroughs remain untested.

Telegram public token and KoBo instance token

telegramBotTokenPublicV1 accepts exactly profile: "telegram-bot-token-public-v1" and the existing accessToken. koboTokenPublicInstanceV1 accepts the existing token with its explicit instance, origin and origin-normalization acknowledgment. See the Telegram account example and KoBo account example. These account types remain distinct from historical imported references and generic credentials; explicitly reselect the supported account after repair.

Named/Advanced JSON Save validates locally, encrypts and remains unverified, with no HTTP or DNS request. Credential Test is unsupported for both; bulk tests skip them without recording a pass or a failure. Current account revision and workspace/organization authority are rechecked during the separately approved workflow request. Saving or testing never sends a sample message, fetches a form or creates an external resource.

AWS Comprehend, SNS and SES requests

AWS Comprehend supports three text analyses; SNS supports topic create, delete and publish; SES supports six custom verification email actions, two email sends and five template actions. These nineteen ordinary version-1 imports require parameter schema 2, explicit migration acknowledgement and an acknowledgement that inputs and operation data persist in workflow history and may reach downstream AI or remote actions. The SNS Trigger lifecycle, Tool variants, extra AWS APIs, attachments and raw MIME are unsupported.

Select the exact manual credential family: awsComprehendManualSigV4V1, awsSnsManualSigV4V1 or awsSesManualSigV4V1. Their profiles are respectively aws-comprehend-manual-sigv4-v1, aws-sns-manual-sigv4-v1 and aws-ses-manual-sigv4-v1. Named fields and Advanced JSON save the same strict account. Supply partition aws, an explicitly supported commercial region, a declared 12-digit account ID, mode, access key ID and secret access key. manual-temporary additionally requires a supplied session token and UTC expiry beyond the 30-second invocation budget plus a 60-second margin. manual-static forbids token and expiry. Save/reopen is local and unverified, performs zero provider HTTP and does not reveal saved secrets. Test is unsupported and bulk Test skips these three families. No STS, role assumption, system provider chain, refresh, account probe, discovery or picker read occurs. The account ID restricts inputs and does not prove AWS identity.

Each run requires a separate exact-request HumanTask approved by the original run actor within fifteen minutes. Another administrator cannot substitute. Current workspace and organization membership, policy, workflow/node/input/account revisions, preference generation, consumed task/wait and lease are checked again at execution and OUTPUT. One checkpoint claim allows at most one physical request. An error, timeout, disconnect, lost settlement or missing receipt leaves an uncertain outcome and never grants automatic resend. HTTP acceptance, MessageId or TopicArn does not prove delivery, processing, verification, topic deletion, remote template state, privileges or identity. Comprehend discloses text; SNS can fan out to existing subscribers; SES may send mail or change remote templates. Charges and downstream effects are possible.

Exact bounded raw response bytes are application-encrypted into WorkspaceFiles and bound to the run, actor, account, request, task/wait and HTTP status. OUTPUT reopens and authenticates that protected artifact under current authority. This does not claim raw database encryption, inspection of plaintext by antivirus, or completed backup/export deletion verification. The configured file scanner sees ciphertext; unavailable storage/scanning prevents a usable result without resending. Operation data, including addresses, templates and other personal information, remains in ordinary workflow history and can reach downstream AI and remote actions. Require rawRetentionAcknowledged:true before execution; do not supply data you cannot retain or disclose through those paths.

These profiles impose local limits below provider limits: 4096 UTF-8 bytes per text/template field, 16 KiB request, 1 MiB response, thirty seconds, sixty-four template-data rows and fifty total destination recipients. Lists are exactly one bounded page, default twenty, at most fifty custom verification templates or one hundred ordinary templates. Require boundedPageAcknowledged:true, returnAll:false and explicit opaque continuationToken for a subsequent separately approved page. No hidden pagination, readback or retry occurs. HTML, redirect and template strings remain inert locally and are never fetched. The supported endpoint maps contain 12 Comprehend, 34 SNS and 27 SES commercial regions. Available regions depend on the selected service.

SNS names and ARNs are bound to the selected commercial region and declared account. FIFO create/delete accepts .fifo; FIFO publish is refused because the ordinary source lacks MessageGroupId. Comprehend retains ordered language/entity arrays, zero scores and numeric spelling in protected raw data; dominant-language simple mode also provides a derived map. SES custom verification update repairs failureRedirectionURL and fromEmailAddress; template HtmlPart is controlled by its own presence, including HTML-only updates. Unknown/hidden original values and original credential references remain in the import source ledger until deliberately repaired. Corrected form encoding replaces the legacy raw query concatenation and JSON-quoted form body. Import, repair, serialize, reopen and reimport do not grant account or provider verification.

The exact ordinary operation IDs are:

• sns.create
• sns.delete
• sns.publish
• comprehend.text.detectDominantLanguage
• comprehend.text.detectSentiment
• comprehend.text.detectEntities
• ses.customVerificationEmail.create
• ses.customVerificationEmail.delete
• ses.customVerificationEmail.get
• ses.customVerificationEmail.getAll
• ses.customVerificationEmail.send
• ses.customVerificationEmail.update
• ses.email.send
• ses.email.sendTemplate
• ses.template.create
• ses.template.delete
• ses.template.get
• ses.template.getAll
• ses.template.update

For example, an HTML-only SES template update uses:

{
  "parameterSchemaVersion": 2,
  "migrationAcknowledged": true,
  "rawRetentionAcknowledged": true,
  "templateName": "existing-template",
  "updateFields": { "htmlPart": "<p>Reviewed replacement content</p>" }
}

HaloPSA existing bearer profile

The exact credential type is haloExistingBearerV1. Its strict JSON fields are profile:"halo-existing-bearer-v1", origin, basePath, accessToken, expiresAt and optional userPassword. The expiry is operator supplied and unverified. Store a password here and reference saved-account-password in a workflow; plaintext workflow passwords are refused. Local encrypted Save and reopen make no provider request and do not verify permissions. See the account and network requirements.

GoToWebinar existing bearer profile

The exact credential type and profile are gotoWebinarExistingBearerV1. Other required fields are accessToken, strict future UTC expiresAt, and decimal-string accountKey/organizerKey. Supply the actual existing token expiry rather than an invented long lifetime. Account and organizer keys preserve int64 digits; input numbers, signs and whitespace are refused. Never include tokens, passwords or returned join URLs in workflow JSON. Named/Advanced JSON Save is encrypted, local and unverified, with no Test or OAuth/token request. See the account prerequisites.

FileMaker manual session profile

Credential type filemakerManualSessionV1 accepts this strict shape in named fields or Advanced JSON:

{
  "profile": "filemaker-data-v1-manual-session-v1",
  "origin": "https://fm.example.invalid",
  "database": "Research DB",
  "apiVersion": "v1",
  "sessionToken": "EXISTING_SESSION_SUPPLIED_BY_OPERATOR",
  "expiresAt": "2099-01-01T00:00:00Z"
}

Use an already acquired session and an exact public HTTPS origin on port 443, without paths, credentials or query strings. database is entered manually and encoded into the v1 API path; expiresAt is an unverified operator assertion. Unknown, duplicate and prototype fields refuse. This profile neither logs in with a username/password nor logs out, refreshes, discovers metadata or performs a connection Test. It requires explicit migration from the original node; Save remains local and unverified. See account setup.

Bitwarden organization bearer session profile

Credential type and profile are bitwardenOrganizationBearerSessionV1. This schematic JSON deliberately contains an invalid expiry placeholder: replace it with the actual existing session's future UTC expiry, organization UUID, nonce and authorized token. Do not invent a token lifetime.

{
  "profile": "bitwardenOrganizationBearerSessionV1",
  "originProfile": "usCloudV1",
  "origin": "https://api.bitwarden.com",
  "organizationId": "11111111-1111-4111-8111-111111111111",
  "sessionNonce": "OPERATOR_SESSION_NONCE",
  "accessToken": "EXISTING_ORGANIZATION_TOKEN",
  "expiresAt": "ACTUAL_FUTURE_UTC_EXPIRY",
  "migrationAcknowledged": true,
  "sessionScopeAcknowledged": true
}

originProfile is usCloudV1, euCloudV1 or selfHostedPublicV1. US origin is exactly https://api.bitwarden.com; EU is https://api.bitwarden.eu. Both clouds forbid serverVersion. Self-host requires it and an explicitly reviewed public HTTPS origin/443 with no path, query, credentials or fragment. regionalMigrationAcknowledged:true is required for EU/self-host; it may be omitted/false for US. sessionNonce is 16–128 ASCII letters/digits/underscore/hyphen; the existing bearer is 16–2048 visible ASCII characters. Both common acknowledgments must be explicitly true.

Unknown/duplicate/prototype fields, invalid UTF-8, unsafe numbers, invalid UTC expiry or expired profiles refuse. Save/reopen neither verifies provider identity nor entitlement. Tokens use the existing encrypted account store and are never embedded in workflow/source JSON. No Test, acquisition, refresh, identity lookup or discovery runs. See account setup.

Cortex and n8n software Public API existing-key profiles

Named fields and Advanced JSON accept these exact shapes (synthetic values):

{
  "profile": "cortexExistingApiKeyV1",
  "origin": "https://cortex.example.org",
  "basePath": "",
  "apiKey": "EXISTING_KEY_ENTERED_ONLY_IN_SETTINGS"
}

{
  "profile": "n8nPublicApiKeyV1",
  "origin": "https://n8n.example.org",
  "basePath": "/api/v1",
  "apiKey": "EXISTING_KEY_ENTERED_ONLY_IN_SETTINGS"
}

The credential type equals the profile string. Origins must be exact public HTTPS443 without path/query/auth/alternate port/trailing slash. Cortex permits an explicitly empty root prefix; n8n requires its configured API-root path. Paths are bounded, without escapes, dot segments or trailing slash; no discovery or silent normalization occurs. Unknown/duplicate/prototype fields are refused. The API key stays write-only in the existing encrypted credential store; Save/update/reopen is local, unverified and zero HTTP/DNS. Neither profile offers Test, refresh, OAuth, schema fetch or key acquisition. Bulk Test skips them. Instance permissions, version, entitlement and n8n API restrictions remain externally unverified. See account setup.

n8n destructive Public API actions

The selected n8n Public API subset now has nine ordinary actions. Delete a credential (credential.delete, n8n_public_api_credential_delete), Delete an execution (execution.delete, n8n_public_api_execution_delete) and Delete a workflow (workflow.delete, n8n_public_api_workflow_delete) each send one destructive WRITE: DELETE /credentials/<credentialId>, /executions/<executionId> or /workflows/<workflowId>, prefixed by the saved API root. There is no query or body. Credential/workflow IDs are explicit 1–256 ASCII letters, digits, underscore or hyphen; execution IDs are positive safe decimal strings. No collection, wildcard or returned URL becomes a deletion target.

The existing encrypted manual API-key profile and unverified instance edition/version/scopes/entitlement/free-trial prerequisites still apply. All three require the initially unset schema-2 migration, raw-retention and one-attempt controls plus destructiveAcknowledged:true, then a separate original-actor Human Task showing the saved account, origin/root, exact DELETE path and named resource ID. Imported string "true", 1, null and invalid objects remain visible and unchecked until explicitly repaired; opening or saving another field never grants consent. Current workspace and organization authority, policy/account revision, original taskId and waitTokenId, immutable request and lease/claim/CAS checks still apply, including later authenticated OUTPUT.

A genuinely empty HTTP204 or HTTP200 response maps to data:{resource,id,response:"empty"}, with zero examined/returned records and outcomeVerified:false; it observes a response and does not prove deletion. HTTP200 expected metadata maps to response:"metadata" and bounded metadata, with an exactly matching target ID. Credential metadata is only id/name/type; execution data omits runData/workflowData/customData; workflow data omits parameters/settings/pinnedData/connections/credential references. JSON null, whitespace, malformed/unexpected bodies, wrong IDs and other statuses are withheld. There is no deleted:true, automatic readback, paging, polling, retry or uncertain-effect replay. Map node.<id>.json.data.id, .response or available .metadata.name/.status; names and IDs may contain PII retained in ordinary history and downstream mappings, without a new raw-database encryption, TTL/deletion or scanner guarantee.

Real deletion effects, provider authentication, durable DB/Redis, native DNS/TLS and matching-revision Review remain untested. Use only separately authorized disposable resources for live verification; existing credentials, workflows and executions are not test targets. Credential create, workflow create/update/activate/deactivate/getVersion and Tool/Trigger remain unavailable; nine actions do not establish full-node parity.

AWS Transcribe job requests and metadata

The partial AWS Transcribe subset supports four ordinary numeric-version-1 actions: transcribe.transcriptionJob.create, transcribe.transcriptionJob.delete, transcribe.transcriptionJob.get and transcribe.transcriptionJob.getAll. Transcript downloading, simplification, automatic language detection, unbounded pagination and Tool/Trigger forms are unsupported. This is partial service coverage, not full-node or provider parity.

Save an existing awsTranscribeManualSigV4V1 account with profile aws-transcribe-manual-sigv4-v1, partition aws, one of twenty pinned standard regions, declared twelve-digit account ID and manual access keys. Named fields and Advanced JSON use the same encrypted, write-only account. manual-static omits token and expiry; manual-temporary requires an explicitly supplied session token and actual UTC expiry, with more than ninety seconds remaining at execution. Save/update/reopen is local and unverified with zero provider HTTP/DNS. Test and bulk Test are unavailable. No ambient/system/role credentials, STS acquisition, refresh, discovery or custom endpoints are used. The declared account does not prove AWS identity.

Import exact n8n-nodes-base.awsTranscribe with numeric typeVersion:1, preserve original parameters and credential references, and repair the schema-2 input deliberately. Select the exact saved account and set the initially unset migrationAcknowledged:true and rawRetentionAcknowledged:true controls. Imported strings such as "true", numbers and null remain invalid, unchecked and preserved until an explicit click or repair. Unknown and inactive fields remain repair items; embedded credentials are refused before source-ledger persistence. Original get defaults to returnTranscript:true; that intent is unsupported and is never silently converted to metadata.

Create requires an explicit unique transcriptionJobName, authorized same-region s3://bucket/key media URI, mediaFormat, detectLanguage:false, supported languageCode and an explicit options object. The original v1 node has no media-format field, so imports require manual format selection. Supported original settings include channel identification, maximum alternatives/speaker labels (2–10), vocabulary name and a complete vocabulary-filter name/method pair. Channel identification cannot combine with speaker labels. Deliberately set the initially unset processingAcknowledged:true: AWS obtains the authorized media, processes speech, may charge costs and retains job/transcript data under its policies; the app never fetches the media URI. A QUEUED or IN_PROGRESS result remains pending. No polling or completed-transcription claim follows submission.

Delete requires the explicit job name and initially unset destructiveAcknowledged:true, then a separate original-actor Human Task showing the exact AWS request. An actual empty HTTP200 body yields empty operationData:{} with responseReceived:true and outcomeVerified:false. It is response evidence only; job deletion completion and transcript object removal are not verified. There is no fabricated success:true, hidden readback or automatic resend.

Get requires returnTranscript:false explicitly. It returns bounded typed job/status/time/media/transcript-location metadata in operationData. Transcript locations remain inert JSON strings, including on COMPLETED jobs: the app never fetches a provider-returned URI or simplifies a transcript. Get All requires explicit returnAll:false, limit 1–100, filters:{} or supported original status/name filters, and boundedPageAcknowledged:true. It returns one partial page envelope with TranscriptionJobSummaries and any actual top-level NextToken. Copy that token into nextToken only for a separate manually approved next request. A short or empty page does not prove exhaustive inventory; the original broken unbounded paginator is not reproduced.

Only the original run actor can approve the exact request within fifteen minutes. Current workspace and organization authority, selected account, published node/version, run input, resolved request, original task ID, wait token, stable durable decision and execution lease are checked through claim, dispatch, settlement and fresh OUTPUT. Replacement never renews consent. One claim permits at most one physical attempt despite workflow retries; timeout, revocation, disconnect, expired lease or uncertain settlement cannot authorize resend. Same-lineage failure cleanup grants no new authority and remains fenced by the real lease.

Local limits are 16 KiB request, 1 MiB whole response, thirty seconds, depth32/nodes20000 and strict unknown-field refusal. Malformed, oversized, unexpected, numerically mistyped or credential-reflecting responses fail closed. Useful job metadata, names and media/transcript locations enter ordinary workflow/checkpoint/Human history and may reach downstream AI. Accepted raw response bytes use the existing encrypted protected Workspace Files mechanism; this adds no raw-database encryption, automatic TTL, plaintext-scanner or deletion guarantee.

En español: selecciona una cuenta manual existente y la acción exacta. Corrige los campos importados y marca cada confirmación deliberadamente. AWS obtiene el archivo autorizado; la aplicación no descarga archivos ni transcripciones. Los trabajos pendientes siguen pendientes, eliminar solo acredita la respuesta y listar devuelve una página parcial con un token manual. Los metadatos y sus ubicaciones pueden conservarse en el historial y llegar a la IA posterior.

Local tests simulate provider/Prisma facts and use actual public resume, Human Task, checkpoint and output owners. Real AWS authentication/permissions/effects, native DNS/TLS, DB/Redis restart, real AI request interpretation and Review workspace/organization Help walkthroughs remain untested because those external environments and credentials are outside this worker's authority. See the official StartTranscriptionJob, DeleteTranscriptionJob, GetTranscriptionJob and ListTranscriptionJobs contracts.

AWS Certificate Manager certificates

The five ordinary numeric-version-1 actions are acm.certificate.delete, acm.certificate.get, acm.certificate.getMany, acm.certificate.getMetadata and acm.certificate.renew. Select AWS Certificate Manager, then the exact certificate action. Tool/Trigger variants, certificate requests/import/export, private-key export and ACME management are unavailable.

Use an encrypted saved awsAcmManualSigV4V1 account with profile aws-acm-manual-sigv4-v1, partition aws, a supported pinned commercial region, declared twelve-digit account ID, access key ID and secret access key. Named fields and Advanced JSON save the same account. manual-static omits session token/expiry; manual-temporary requires the actual supplied session token and UTC expiry; execution requires more than ninety seconds remaining. Local Save can retain an expired profile as unverified, but execution refuses it without refresh. The current bounded endpoint profile supports the same twelve explicitly pinned regions as Comprehend; other regions and partitions require a separate profile. The declared account ID restricts the certificate ARN and is not verified identity. Save/update/reopen is local, encrypted, write-only and unverified, with zero provider HTTP/DNS. Test and bulk Test are unavailable. No automatic STS, AssumeRole, system credentials, refresh, custom/FIPS/dualstack endpoints or discovery occurs.

Import n8n-nodes-base.awsCertificateManager with numeric typeVersion:1, preserve its original node/parameters/credential references, then reselect the native account and repair schema 2 explicitly. Unknown and inactive values stay visible and refuse execution. Embedded credential material is refused before source-ledger/workflow persistence. Original authentication:iam maps to the manual account lifecycle; AssumeRole/system/custom endpoint settings require manual repair. Remove the original unused S3 bucketName and certificateKey fields explicitly; they never become ACM request fields. The original default renew is not consent. Portable imports and exports can retain non-secret domain/certificate business data and original references.

Set parameterSchemaVersion:2, migrationAcknowledged:true and rawRetentionAcknowledged:true. Acknowledgments start unset, require literal boolean true and retain imported string "true" as invalid and unchecked until explicitly repaired. Delete also requires destructiveAcknowledged:true; renew requires providerEffectsAcknowledged:true. The exact certificate ARN must match the selected region/partition/account. Only the original run actor can approve the exact named request within fifteen minutes, with current workspace AND organization authority. The runtime captures the original task ID, wait token and durable decision at resume production, then loads that original task by ID throughout claim, send, settlement and fresh OUTPUT. A replacement task, wait, decision, account, node or input cannot renew consent. The execution lease remains required; an expired lease cannot weaken the physical-claim or cleanup fence.

Delete removes the certificate and associated private key; an in-use certificate cannot be deleted. AWS documents eventual consistency and unchanged Private CA billing. Renew requests renewal of an eligible certificate and can require Private CA permissions and incur costs. Both are writes: an empty HTTP 200 proves only that the response was observed, and the result retains outcomeVerified:false. There is no completed-deletion/renewal claim, readback, polling or certificate acquisition. Get returns only valid certificate PEM blocks and optional certificate chain. Get Metadata returns useful bounded exact certificate/domain/subject/contact/status/time/algorithm/type data. Those fields remain available for downstream mapping.

Get Many reads exactly one page, with original limit 1–500/default100, returnAll:false and boundedPageAcknowledged:true. Preserve the nested original options.certificateStatuses, options.extendedKeyUsage, options.keyTypes and options.keyUsage arrays. Extended Key Usage applies independently of status, correcting the original gate. Omit unused filters; explicit empty arrays require repair. AWS defaults restrict types to RSA_2048 and omit ACME origins, so a short/empty page does not prove exhaustive account inventory. NextToken remains returned business data and is not followed. Return All, continuation input and newer sort/origin/export filters require separate explicit extensions.

Local bounds are 16 KiB request, 1 MiB whole response, thirty seconds, depth32/nodes20000 and one physical attempt, even when workflow retries are configured. AWS permits a GetCertificate chain up to 2 MiB; this application's narrower whole-response bound refuses a valid oversized chain without truncation or fabricated success. Malformed/duplicate/invalid JSON, unexpected fields/status, credential reflections, private/reserved origins and partial responses fail closed. Once claimed, a timeout, disconnect, parser/storage failure or uncertain outcome never permits replay through a new gateway.

Exact accepted business output, inputs, domain names, ARNs, subjects, validation contacts and certificate PEM may remain in ordinary run/checkpoint/Human history and reach downstream AI or remote actions. Accepted raw response bytes are application-encrypted into protected Workspace Files and authenticated at fresh OUTPUT; the configured scanner sees ciphertext. This supplies no raw database encryption, automatic TTL, plaintext scanner or deletion-completion guarantee. Invalid responses and credential/error reflections do not become accepted business output.

For example, one partial list uses:

{
  "parameterSchemaVersion": 2,
  "migrationAcknowledged": true,
  "rawRetentionAcknowledged": true,
  "returnAll": false,
  "limit": 100,
  "boundedPageAcknowledged": true,
  "options": { "extendedKeyUsage": ["TLS_WEB_SERVER_AUTHENTICATION"], "keyTypes": ["RSA_2048"] }
}

An explicitly acknowledged deletion names its certificate:

{
  "parameterSchemaVersion": 2,
  "migrationAcknowledged": true,
  "rawRetentionAcknowledged": true,
  "certificateArn": "arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012",
  "destructiveAcknowledged": true
}

En español: elige la acción exacta y una cuenta manual guardada, corrige los campos importados y marca cada confirmación deliberadamente. El actor original confirma el ARN y la solicitud; HTTP 200 solo demuestra una respuesta, no la eliminación ni la renovación finalizadas. Una lista lee una página parcial y los datos del certificado permanecen disponibles para pasos posteriores con la retención habitual.

Local tests use simulated provider/store boundaries. Real AWS permissions/eligibility/effects, native DNS/TLS/provider execution, durable DB/Redis restart, storage scanning and Review workspace/organization Help walkthroughs remain untested. See the official DeleteCertificate, GetCertificate, ListCertificates, DescribeCertificate and RenewCertificate contracts.

DynamoDB typed items

Select AWS DynamoDB for the four ordinary numeric-version-1 operations dynamodb.item.upsert, dynamodb.item.delete, dynamodb.item.get and dynamodb.item.getAll. These use PutItem, DeleteItem, GetItem and an explicit Query or Scan. This is a partial service integration; automatic mapping, simplified decoding, discovery, Tool/Trigger variants and other APIs are unavailable.

Save awsDynamoDbManualSigV4V1 with profile aws-dynamodb-manual-sigv4-v1, partition aws, one of twelve pinned commercial regions, a declared twelve-digit account, and manual static keys or the supplied temporary session token with its actual UTC expiry. Temporary execution requires more than ninety seconds remaining. Named fields and Advanced JSON save/update/reopen the same encrypted write-only, locally unverified account with zero provider HTTP/DNS. Test and bulk Test are unavailable; no SDK, environment/metadata discovery, role assumption, STS acquisition, refresh or custom/FIPS/dualstack endpoint runs. A declared account is not verified AWS identity.

Import exact n8n-nodes-base.awsDynamoDb with numeric typeVersion:1. Original parameters, raw JSON types and credential references remain retained through edit, serialize, reopen and reimport. Reselect the typed saved account and deliberately repair parameterSchemaVersion:2, typed item/key/expression fields and unsupported legacy options. Embedded credential controls are refused before source-ledger persistence; ordinary typed database attribute names remain business data. The initially unset migrationAcknowledged, rawRetentionAcknowledged and onePhysicalAttemptAcknowledged must each be literal boolean true. Imported "true", 1 or null is never consent.

PutItem is full replacement, including removal of omitted attributes on an existing item with the same key. Supply the complete typed item and explicit replaceAcknowledged:true. Delete requires an exact typed key and deleteAcknowledged:true; choose returnValues:NONE or ALL_OLD. Both also require a separate original-actor Human Task for the exact table/item or key, conditions, account and consequences. Conditions can fail without retry or hidden readback. acknowledged:true, submitted input and returned old attributes observe the response; remotePersistenceVerified:false and outer outcomeVerified:false remain explicit. They never prove remote persistence.

AttributeValue JSON preserves S, exact decimal-string N (up to38 significant digits within the documented range), strict padded base64 B, BOOL, NULL:true, nonempty unique SS/NS/BS, L and M, including empty lists/maps. Primary keys use nonempty scalar S/N/B values. Attribute names and table schema are entered manually, without discovery. Set/list and data-name bounds may be narrower than AWS. GetItem allows explicit consistency and projection aliases; a missing Item returns found:false, while malformed or unexpected bodies fail closed.

Get All requires an explicit mode:Query with keyConditionExpression, or mode:Scan; index, filter, projection, aliases and typed values are manual. Set returnAll:false and limit:1..100: Limit counts evaluated items, not returned items or a cost guarantee. Exactly one bounded page is read. An empty filtered Items array can still return a typed lastEvaluatedKey; copy it to exclusiveStartKey only in a new, separately confirmed request. select:COUNT returns a count/scanned-count object, never an array. COUNT cannot include a projection. pageComplete means this response had no continuation key, not snapshot or exhaustive-inventory proof.

Local whole-input/request bounds are64KiB, whole response1MiB, depth32,20000nodes,4096reads and thirty seconds. Inherited32KiB signed approval and48KiB Human instructions can impose a smaller effective input. Oversized, missing, malformed, duplicate or unexpected bodies are refused without truncation. One durable physical claim remains bound to the actual public resume producer's original task ID, wait token and durable decision, current workspace and organization authority, account/input revision and live acquired lease through settlement and fresh authenticated OUTPUT. Expired ownership or an uncertain used claim cannot replay through a new gateway; unchanged-lineage failure cleanup uses the execution-lease CAS fence.

Table names, keys, attribute names and item data may be PII retained in ordinary workflow/checkpoint/Human history and downstream mapping or AI. Account encryption adds no raw-database encryption, automatic TTL/deletion or scanner guarantee. Local tests simulate provider/store facts; live AWS, native DNS/TLS, real DB/Redis restart, real AI phrasing and matching-revision Review workspace/organization Help walkthroughs remain untested. See official GetItem, DeleteItem and AttributeValue contracts.

AWS ELB ordinary actions

The exact awsElbManualSigV4V1 JSON profile is aws-elb-manual-sigv4-v1 with partition aws, pinned region, declaredAccountId, mode, accessKeyId and secretAccessKey. manual-static forbids token/expiry; manual-temporary requires supplied sessionToken and actual UTC expiresAt. Secrets remain encrypted/write-only and replacement invalidates approvals. Save/update/reopen sends zero HTTP/DNS and stays unverified; no Test, STS, ambient/system/role/metadata credentials, acquisition or refresh. See actions, controls, limits and repair policy. Real AWS effects, native transport, durable DB/Redis and matching Review tutorials remain untested.

AWS Cognito User Pools manual credentials

Use awsCognitoManualSigV4V1 with profile aws-cognito-manual-sigv4-v1, partition aws, supported pinned region, declaredAccountId, mode, accessKeyId and secretAccessKey. manual-temporary additionally requires sessionToken and its actual UTC expiresAt; static mode omits both. Settings uses encrypted write-only local unverified Save/update/reopen, with zero provider HTTP/DNS. Test and bulk Test are disabled. This is an IAM admin credential profile, not OAuth/authentication/login or automatic STS. See supported regions, limits and consequences.

AWS IAM identity and membership actions

The ordinary numeric-v1 IAM user/group subset covers twelve actions only. It uses the dedicated awsIamManualSigV4V1 account: profile aws-iam-manual-sigv4-v1, partition aws, signing region us-east-1, and fixed global https://iam.amazonaws.com/ over HTTPS443. Use named fields or Advanced JSON for manual static keys, or a supplied temporary token with its actual UTC expiry. Save and reopen are encrypted, write-only, local and unverified; Test is disabled. No ambient, system, role, metadata, STS, credential acquisition or refresh is used.

Exactly one requested Action is sent by form POST with Version 2010-05-08. Identity, access and membership changes require explicit acknowledgments and a separate original-actor Human confirmation. DeleteUser/DeleteGroup fail on provider dependencies; they never remove memberships, login profiles, MFA, policies or access keys implicitly. Membership add/remove are separate exact user/group operations. CreateUser supports path, tags and permissions boundary; updates support path and rename only. No policy, role, access-key or login-password CRUD is added. HTTP200 is provider response evidence, never verified effect completion.

Lists require explicit returnAll: false, limit 1–1000 and bounded-page consent. GetGroup also pages Users; IsTruncated and opaque exact Marker remain visible even when Users are omitted. Continue only with another separately approved request. No automatic paging, membership scans, discovery, loaders, post-read, retries, returned-URL fetching or redirects. Original helper, returnAll and includeUsers semantics that cannot be preserved remain visible for manual repair; unknown fields and invalid consent types survive export/reopen. Embedded credentials are refused before source-ledger persistence.

Typed user/group identity, ARN, path, creation time, tags, boundary and explicitly selected membership data plus an exact raw reference enter ordinary run/checkpoint/Human history and may reach downstream AI. Account encryption adds no raw database encryption, automatic TTL or scanner guarantee. A bounded XML decoder rejects DTD, external/custom entities, duplicate or wrong envelopes, malformed members, unknown fields/status and credential reflection before retaining raw data. Current workspace and organization permissions, account, input, policy, immutable original task/wait/decision and lease are rechecked through claim, send, response, settlement and fresh OUTPUT. Uncertain or expired claims cannot resend. Local bounds: 32 KiB request, 1 MiB response, 30 seconds. Real AWS, hosted Review and full node/provider parity remain untested.

AWS S3 ordinary bucket subset

The partial ordinary S3 subset covers only s3.bucket.create, s3.bucket.delete, s3.bucket.getAll and s3.bucket.search: four of twelve actions, with exact numeric source V1/V2 imports analyzed separately. Search is ListObjectsV2 object metadata, not a bucket-name search. Object upload/download/copy/delete, folder deletion, multipart, Tool and Trigger remain unsupported.

Save awsS3BucketManualSigV4V1 / aws-s3-manual-sigv4-v1 with partition aws, an explicitly known us-east-1 or eu-west-1 region, declared twelve-digit account ID and manual static keys or supplied temporary token plus actual UTC expiry. Temporary execution needs over ninety seconds remaining. Named fields and Advanced JSON use encrypted, write-only, unverified local Save/update/reopen with zero provider HTTP/DNS. Test, bulk Test, STS, system/role chains, refresh, custom endpoints and discovery are unavailable.

Every request requires schema2 and initially unset migrationAcknowledged, rawRetentionAcknowledged, regionAcknowledged and billingAcknowledged, all literal true, plus action-specific consent. Raw string "true", 1, null and objects remain visible and unchecked until a deliberate click. Then a separate original-actor Human Task approves the exact request. Current workspace and organization access, account, node, input, policy, original task ID/wait token/stable decision and real execution lease are checked through the one durable claim, send, response, settlement and fresh OUTPUT. Expired or uncertain claims never replay.

Create requires name, additionalFields:{} (or a matching known region) and name/global-namespace/security/write acknowledgments. It sends one PUT: empty body for us-east-1, matching XML LocationConstraint elsewhere. Only provider secure defaults are supported; all original ACL/grant/ownership/tag/object-lock intent stays for explicit repair. HTTP200 empty body yields response evidence with effectConfirmed:false; Location remains inert manual metadata. Creating an existing owned us-east-1 bucket can reset ACLs under AWS behavior; inspect the exact name and permissions manually before approval.

Delete requires name, empty-bucket/global-namespace/destructive acknowledgments and sends one DELETE. The bucket must already be empty of objects, versions and delete markers; nothing enumerates or deletes them or changes protection/ownership. Only HTTP204 empty body is accepted as response evidence, never confirmed deletion. A deleted global name may be reused by another account.

ListBuckets (getAll) needs explicit returnAll:false, limit:1..1000, filters:{} and boundedPageAcknowledged:true. This is a local cap, not the AWS maximum10000. Optional filters.bucketRegion must equal the endpoint region; filters.prefix filters bucket names. Output preserves actual ContinuationToken; copy it byte-for-byte into nextToken for a separately approved request. Unpaginated accounts with approved quota above10000 may be rejected; no auto-page or local slice is used.

ListObjectsV2 (search) needs bucketName, explicit returnAll:false, limit:1..1000, additionalFields:{}, bounded-page and Requester Pays acknowledgment. Supported typed options are prefix, delimiter, encodingType:url, fetchOwner, startAfter and requesterPays; the payer is a header. Dotted names use regional HTTPS443 path style. Output keeps bounded Contents, CommonPrefixes, KeyCount, IsTruncated, keys, ETags, sizes, storage classes, dates and actual NextContinuationToken; tokens and keys remain inert values. No content or returned URL is fetched. Empty XML containers and singleton/many entries normalize without fabricated rows.

Original versions keep exact parameters and credential references. V1 ignores the location region during signing; V2 forwards it and handles dotted search names differently. Both original location reads, null/us-east-1/EU assumptions, returnAll/default/limit and unsupported options require visible manual repair. No hidden GetBucketLocation/HeadBucket/readback, redirect, follow-up, polling or retry occurs. Local32KiB request/1MiB response/thirty-second bounds apply; malformed, duplicate, DTD/entity/XXE, wrong-envelope, oversized or credential-reflecting replies fail before accepted artifact retention. Useful metadata and tokens enter ordinary run/Human history and downstream AI; account encryption adds no raw DB encryption, TTL or scanner guarantee.

En español: selecciona una cuenta manual existente y una región conocida, corrige el origen V1/V2 y marca cada confirmación de forma deliberada. Crear y eliminar solo acreditan respuestas; listar devuelve una página parcial y buscar lista metadatos de objetos. Copia el token exacto para otra solicitud aprobada. No se descargan objetos ni se eliminan sus versiones.

Local tests simulate provider/Prisma facts. Real AWS credentials, permissions/effects, native DNS/TLS, DB/Redis restart, AI request interpretation and Review workspace/organization Help walkthroughs remain untested because they are outside this worker's authority. See CreateBucket, DeleteBucket, ListBuckets and ListObjectsV2.

TheHive v1 manual case reads

TheHive and TheHiveProject are two imported wrappers of one Query API service. Only exact ordinary version-1 n8n-nodes-base.theHive and n8n-nodes-base.theHiveProject with explicit case/get are supported. Choose case.getLegacy with theHiveApi and explicit apiVersion: "v1", or case.getProject with theHiveProjectApi. Legacy input is { "id": "~case-id" }; Project input is { "caseId": "~case-id" }. Project also accepts the original manual ID locator. Tool/Trigger variants, missing versions, v0, writes, options, arbitrary queries, list/URL locators, loaders, binary and asynchronous actions require manual repair. Original source controls remain retained and checked.

Save an existing API key with an explicit public HTTPS origin (no subpath, credentials, query, fragment or custom port), exact wrapper profile and an explicit organization policy:

{
  "profile": "theHiveApi",
  "apiVersion": "v1",
  "url": "https://incident.example.org",
  "ApiKey": "SYNTHETIC_EXISTING_API_KEY",
  "organization": { "mode": "named", "name": "responders" },
  "allowUnauthorizedCerts": false
}

For Project, use profile: "theHiveProjectApi" and omit apiVersion. Named fields and Advanced JSON use the same validator; save, update and reopen are local and unverified, with zero provider HTTP. Test and bulk testing are unavailable. Choose { "mode": "default" } explicitly to use the API key owner's default organization, or named scope to send X-Organisation. The application does not discover or verify that organization. A private-only installation is outside this public-origin policy; deployment outbound policy and reachability remain unverified.

Both reads need a separate signed 15-minute Human Task decided by the original run actor. Current workspace and organization membership, account, workflow, input, policy, task, wait, durable decision and execution lease must still match. One physical claim permits one bounded POST to /api/v1/query?name=get-case-…; retries, polling, paging, refresh and returned-link fetching are unavailable even if node retries are enabled. Legacy sends only getCase; Project adds exactly page 0 to 10 with extraData: ["attachmentCount"].

Outputs retain the wrapper's sourceIdentity, case ID, case number, title, unknown business fields and Project attachment count. Zero results return kind: "no-record"; incomplete/malformed/error/mismatched responses are refused. Numeric tokens that cannot pass the explicit precision policy are refused instead of rounded. Only a fully validated bounded response may be retained as an application-encrypted Workspace File; the configured scanner sees ciphertext. Useful business data can persist in workflow history and downstream steps. Fresh OUTPUT admission verifies current authority and the exact signed receipt and raw artifact, with no resend after uncertainty. Installed API version, provider acceptance, key permissions, actual organization visibility, native network behavior and matching-revision Review remain unverified; this is partial support.

Odoo contact reads

The exact odooApi JSON shape is {url,db,username,password}. url is a root public HTTPS DNS origin on443 with no userinfo, path, query or fragment; db is always explicit. password accepts an existing password or RPC API key of at least eight characters. No inferred database, OAuth, token acquisition, credential Test or automatic refresh. Named/Advanced Save is local, encrypted, write-only and unverified.

Deployment/version, Custom plan, model, ACL and public reachability are unverified. Local provider/Prisma facts are simulated; real provider/native/DB/Review organization and workspace behavior is untested. See the complete bounded protocol and limitations.

Flow task/get partial compatibility

Only ordinary n8n-nodes-base.flow numeric typeVersion1 task/get is supported. This is partial compatibility derived from the shipped node and helper, with live protocol and account entitlement unverified. A bounded unauthenticated GET of the official developer documentation failed DNS ([Errno 8] nodename nor servname provided, or not known); that failure does not show provider retirement.

Save flowManualBearerV1 with named fields or Advanced JSON: {"profile":"flowManualBearerV1","organizationId":"701","accessToken":"YOUR_EXISTING_TOKEN"}. Enter secrets only in the encrypted account editor. Save/update/reopen is local, write-only and unverified with zero provider HTTP; Test is unsupported and bulk Test skips it. No OAuth, token discovery, acquisition or refresh occurs. Provider organizationId is independent of application organization/workspace IDs and never inferred from them.

Use task.get with parameterSchemaVersion:2, migrationAcknowledged:true, rawRetentionAcknowledged:true, onePhysicalAttemptAcknowledged:true and one exact positive decimal taskId. A safe integer input is accepted; unsafe numbers refuse rather than round. Decimal strings preserve large IDs. Optional filters.include accepts only schedule, files, file_associations, parent, at most once each. Example: {"parameterSchemaVersion":2,"migrationAcknowledged":true,"rawRetentionAcknowledged":true,"onePhysicalAttemptAcknowledged":true,"taskId":"9007199254740993123","filters":{"include":["files"]}}. Acknowledgments start unset and require explicit review. Unknown optional controls remain visible manual repair intent; imported source parameters, versions and credential references remain in a source ledger. Reselect the typed saved account deliberately.

The original actor with current workspace AND application organization authority separately approves exactly one GET https://api.getflow.com/v2/tasks/{taskId}?organization_id={credentialOrganizationId} with Bearer accessToken. Original task ID, wait token, stable decision revision, actor/account/input/node/policy and execution lease remain bound through one physical claim CAS, response, settlement and fresh OUTPUT. Ambiguous responses, changed ownership or expired leases never grant a resend, including with node Retry enabled. Local limits are thirty seconds, 1MiB response, depth32 and 20k nodes; these are not provider limits. Self-hosted outbound reachability remains unverified.

Use data.task and optional included entities from the intact response envelope. Unknown useful business fields remain available; every provider JSON number is represented as its exact original text, including precision and exponent spelling. Original source IDs are not replaced by labels or application IDs. Accepted raw UTF-8 is application-encrypted in scoped WorkspaceFiles and represented by rawReference; plaintext raw/sourceItems are absent from ordinary output. Business data can remain in workflow history and downstream mappings/AI. The scanner sees ciphertext, not plaintext; no raw-database encryption, deletion deadline or backup deletion claim is made. Invalid envelopes, business errors, missing/mismatched tasks, auth/status/transport/rate failures, duplicate JSON, oversize bodies, invalid UTF-8 and secret reflection refuse success and accepted raw retention.

Create/update/getAll, triggers, webhooks, dynamic loaders, paging, Link helpers, retries, polling, readback and returned-URL fetch are unsupported. Mocked provider and Prisma facts do not verify live Flow, native DNS/TLS, durable DB/Redis, real AI or Review workspace/organization walkthroughs.

Azure Cosmos DB: get one existing container

The three acknowledgment switches start unchecked on a new or original n8n import. Choose each explicitly. Only literal boolean true counts as consent; imported strings such as "true", other invalid JSON values and expressions remain invalid through unrelated edits and export/reopen until explicitly repaired.

The original read contract for provider azure-cosmos-db exposes container.get / tool cosmos_container_get, with ordinary numeric n8n version 1 container/get migration. Use the exact azureCosmosDbMasterKeyV1 encrypted manual account containing profile, public account, explicit case-sensitive database and existing canonical base64 key. Save/update/reopen is local, write-only and unverified; zero HTTP and no Test/OAuth/managed identity/connection string. Input requires parameterSchemaVersion:2, explicit container, migrationAcknowledged:true, rawRetentionAcknowledged:true and onePhysicalAttemptAcknowledged:true.

One original-actor Human confirmation binds the account ID/revision, database, container, origin and retention. Current direct organization AND workspace membership, exact account, current lease, independent WORKFLOW_LIVE_AZURE_COSMOS_DB=true and workspace live preference are rechecked. One durable effect claim and consumed-decision annotation precede one HMAC GET collection; no retry or replay after uncertainty. Limits: total 30 seconds, 1 MiB, depth 32 and 20000 nodes. Use data.container; metadata and unknown business fields persist in ordinary history and downstream mapping, while raw transport text is discarded. Actual key/signature echoes and malformed/status/identity failures refuse success.

Original defaults/options outside this read contract require visible manual repair; no item probes, writes, query, pagination, Tool/Trigger, private/custom/sovereign origin or returned-link fetch. SQL/NoSQL API, local auth, rights, RU charges, network ACLs, real Azure, native deployment, durable DB/Redis restart and Review remain unverified. See the full credential, import and runtime contract.

X (Twitter v2): one username lookup

The useful native unit is exact ordinary numeric typeVersion: 2 user.searchUser, using one explicit username of 1–15 ASCII letters, digits or underscores. It sends one GET https://api.x.com/2/users/by/username/{username} with no query or body. The current documented hostname differs from original api.twitter.com; support for that old alias remains unverified, and redirects are refused. Original default tweet/resource conversion, v1/OAuth1, me/ID lookup, writes, extra fields, expansions, multiuser, paging and retries are visibly unsupported. Import retains original source ledgers and requires explicit repair and account reselection.

In Connections, choose X (Twitter v2) and enter your existing bearer in the named accessToken field, or Advanced JSON {"profile":"xUserV2ManualBearerV1","accessToken":"YOUR_EXISTING_TOKEN"}. Save/update/close/reopen use existing encrypted storage, remain unverified and send zero HTTP/DNS. Test is unsupported and bulk Test skips this account. OAuth2 PKCE acquisition/refresh and original OAuth or broad-scope aliases are not provided. Current X endpoint authorization and credits/pay-per-use require a suitable account; actual grants, entitlement, credits and visibility remain unverified without a real provider test.

In Builder, select user.searchUser, the exact saved workspace account and the username, and explicitly check migrationAcknowledged, outputRetentionAcknowledged and onePhysicalAttemptAcknowledged with schema version2. Current workspace live preference AND the operator WORKFLOW_LIVE_TWITTER gate are required. The original actor needs current organization AND direct workspace execution membership and confirms the exact material in a separate Human Task. Current account bytes, identity, original wait/decision, workflow/version/input, consumed resume segment and nonempty owned lease are checked before the physical claim, HTTP and output persistence. Rotation, deletion, retyping, deauthorization, membership/live changes, later resume/retry/recovery, removed/tampered claims and expired leases refuse further dispatch; uncertain outcomes never automatically replay.

The bounded original data user object is returned as data and one original-style item in sourceItemsJson. String snowflake data.id keeps precision. data.name, data.username and bounded unknown nested business fields are available to ordinary output, run history and downstream mappings, and may contain personal information. The raw response envelope and unknown outer fields are discarded; no plaintext raw artifact or new encryption purpose is introduced. Returned URLs remain inert. Explicit credential VALUES (including encoded forms) are refused on reflection; unrelated business field names are retained. Not-found, rate-limit, credits, auth, duplicate keys, malformed/unsafe values and partial errors fail instead of returning an empty user.

Local bounds are one physical attempt, total30s, response1MiB, depth32 and20k nodes. These are local bounds, not vendor quotas or a deletion/scanning guarantee. Current provider service, Review organization walkthrough, native DNS/TLS and durable DB/Redis restart are untested; local HTTP/Prisma/DOM simulations do not establish them.

PayPal: one payout item read

The native partial operation is ordinary n8n-nodes-base.payPal, numeric typeVersion: 1, payoutItem.get. It sends exactly one GET /v1/payments/payouts-item/{payoutItemId} on the saved explicit live (https://api-m.paypal.com:443) or sandbox (https://api-m.sandbox.paypal.com:443) environment. Enter one explicit string ID; numeric coercion, paths, query controls and returned links are refused.

Save a dedicated PayPal account through Named fields or Advanced JSON:

{
  "profile": "paypalPayoutItemManualBearerV1",
  "environment": "sandbox",
  "accessToken": "YOUR_CURRENT_MANUALLY_SUPPLIED_TOKEN"
}

Both editors use the same central validator. Save, update, close and reopen are local encrypted, write-only and unverified, with zero provider HTTP or DNS. Test is unavailable and bulk Test skips this profile. The original payPalApi client ID/secret credential and its hidden authorization POST are separate and unsupported. No OAuth acquisition or refresh occurs; replace an expired manual token yourself. sanbox, omitted environments and arbitrary fallbacks are refused. PayPal Payouts enablement, token expiry, merchant transaction visibility, current permissions and quota remain unknown without real account verification. The application's organization is distinct from the PayPal merchant identity.

Use parameterSchemaVersion: 2, an explicit payoutItemId, and independently check migrationAcknowledged, outputRetentionAcknowledged and onePhysicalAttemptAcknowledged. These acknowledgments start unset. Imported unsupported resources, versions, extra parameters and original credential references remain visible in the source ledger for manual repair and explicit account reselection. Only the original actor with current direct workspace and organization membership can approve the exact account, environment, route and retention in a separate Human Task. Current saved account material, live environment gate WORKFLOW_LIVE_PAYPAL, workspace preference, original task/wait/decision, resume segment and lease are rechecked at claim, dispatch, settlement and output admission. A removed or changed effect record, expired lease, deletion, rotation, retyping, deauthorization or lost membership cannot authorize a resend or account fallback.

The useful single payout-item object appears in result.data and the one-element result.items array. It retains string identifiers, nullable values and nested unknown business fields, including recipient and financial data, in ordinary execution history and downstream mappings. Review those fields before sending them to another action or AI step. The bounded raw HTTP text and transport envelope are discarded after parsing; no encrypted raw-response archive, new TTL, deletion or scanner guarantee is added. Exact credential values echoed in any key or value are refused; business fields are not removed because of their names. Provider errors and not-found responses are failures, while a payout item's documented business status such as FAILED is preserved as business data.

One consumed decision permits one physical request with a total real 30-second deadline, 1 MiB response, depth 32, 20,000-node and finite-read limits. Duplicate JSON keys, invalid UTF-8/media/status, numeric precision loss, overflow, redirects and ambiguous outcomes fail closed with no automatic retry. Payout create/get/list, payout-item cancel, other resources, triggers, dynamic loaders, pagination, returned-link fetching and token acquisition/refresh remain unsupported. This one selected read is not complete PayPal parity. Tests use simulated HTTP/Prisma/DOM facts; real PayPal, native DNS/TLS, a durable database restart, real AI interpretation and the matching authenticated Review workspace/organization tutorial walkthrough remain untested.

Primary endpoint contract: PayPal payout item details.

Microsoft Dynamics: one Dataverse account read

The partial native action is ordinary n8n-nodes-base.microsoftDynamicsCrm, numeric typeVersion: 1, account.get, for one explicit GUID. It sends one GET /api/data/v9.2/accounts(GUID) on the saved HTTPS {environment}.crm.dynamics.com origin at port443. Other regions, sovereign clouds, alternate hosts, select/expand, lists, writes, loaders, Tool/Trigger variants, redirects and retries are unsupported.

Save the dedicated dynamicsAccountManualAccessTokenV1 profile through Named fields or Advanced JSON. Supply accessToken, an exact environmentOrigin, identical declared audience, and a safe-integer declared expiresAtMs in Unix milliseconds. Save/update/reopen are encrypted, local, write-only and unverified with zero provider HTTP/DNS. Test and OAuth acquisition/refresh are unavailable. Historical microsoftDynamicsOAuth2Api and its helper's id_token choice are distinct unsupported authentication. The declarations do not verify a token signature, real audience, actual expiry, tenant consent, Dataverse licensing/security roles or account permission. Replace an expired manual token yourself; at least30 seconds of declared lifetime must remain at execution.

Set parameterSchemaVersion: 1, one accountId, and independently check the initially unset migrationAcknowledged, rawRetentionAcknowledged and onePhysicalAttemptAcknowledged controls. Source values never preaccept application consent. Unsupported original fields, raw versions and credential references remain in the source ledger for manual repair and exact account reselection. The original actor with current direct workspace AND organization membership confirms the precise account, environment, request and retention in a separate Human Task. The application's organization does not establish a Dataverse tenant identity. Current account/secret revision, actor/memberships, live WORKFLOW_LIVE_DYNAMICS and workspace preference, pinned node/input/policy, original task/wait/stable decision, owned lease, checkpoint attempt and native resume segment bind one physical CAS claim and fresh output admission. Used or ambiguous claims never authorize a resend.

result.data and the one-element result.items preserve the bounded account record, string identifiers, nulls, annotations, unknown nested business values and inert prototype-shaped keys. result.rawJson and result.numericLexemes preserve source numeric spelling and JSON Pointer paths because JavaScript numeric projections can round or underflow. Raw JSON and business/personal fields enter normal execution history and downstream values; review retention before acknowledging or forwarding them. Returned links remain data and are never fetched. Exact credential-value echoes are refused without a business-field-name blacklist.

The total request deadline is30 seconds, with1 MiB UTF-8 response, depth32,20,000 parsed value nodes,4,096 properties per object,131,072 string code units and4,096 stream reads; the full output has its own6 MiB/20,000-node copy limits. Duplicate JSON keys, invalid UTF-8/media/status, nonfinite numeric conversion and mismatched account IDs refuse. No real Dataverse request, provider entitlement, live DNS/TLS, durable database restart, AI interpretation or authenticated Review workspace/organization walkthrough was performed. Local tests use simulated provider, Prisma and socket facts.

Primary contract: Dataverse retrieve a row and Dataverse OAuth access tokens.

To replace a saved account, reopen it, re-enter the complete valid profile in Named fields or Advanced JSON and choose Update account. This updates the same account ID and keeps its replacement secret encrypted, write-only and unverified; reopening never reveals the saved token. Advanced JSON and Named fields share the exact profile validator.

Documented application/json; odata.metadata=minimal responses and optional UTF-8 charset are accepted; duplicate or unknown media parameters refuse.

S3-compatible manual account

Credential type genericS3ManualSigV4V1 uses profile generic-s3-manual-sigv4-v1, origin, region, literal boolean pathStyle, mode, accessKeyId and secretAccessKey. mode:"manual-static" omits token and expiry; mode:"manual-temporary" additionally requires sessionToken and exact UTC expiresAt. This account belongs to the separate generic-s3 first-page provider, not the AWS S3 bucket provider. The existing credential create/update routes validate and encrypt the complete supplied JSON locally; summary responses and reopened forms contain no stored secret material. Save is unverified with zero provider HTTP/DNS. Test is unsupported before decrypt/dispatch, bulk Test skips the account, and no token acquisition or refresh occurs. See the manual account instructions.

Redis manual external TLS account

redisManualTlsV1 accepts exact JSON profile:"redis-manual-tls-v1", a public DNS host, numeric port and database, explicit username, existing password, tls:true and rejectUnauthorized:true. An empty username means password-only AUTH; a nonempty username means ACL AUTH. Named fields and Advanced JSON use the same local validator. Save/update/reopen is encrypted, write-only and unverified, with zero DNS, HTTP or socket calls; Test is unsupported and bulk Test skips this type. Queue/infrastructure credentials, account discovery, plaintext and verification disablement are unavailable.

The selected account revision binds an independent original-actor Human approval and one leased CAS claim for explicit AUTH/SELECT plus one string GET. No retry, reconnect or credential refresh occurs. These local controls do not establish actual Redis authentication, permission, native TLS or Review behavior. See the account and execution contract.

Xero: one existing-tenant contact read

The native ordinary numeric version1 subset is contact.get: one GET https://api.xero.com/api.xro/2.0/Contacts/{contactId} with an explicit UUID and Xero-tenant-id. Save the exact xeroContactManualTokenV1 JSON profile with tokenKind: "oauth2-access-token", manually supplied accessToken, existing tenantId and granted contactsScope (accounting.contacts.read or accounting.contacts). The external Xero tenant is distinct from the current application organization. Named fields and Advanced JSON Save/update/reopen are encrypted, write-only, local, unverified and send zero HTTP/DNS; Test and bulk Test skip. No OAuth refresh or tenant discovery.

All seven explicit boolean migration, output-retention, one-attempt, selected-account, tenant-authorization, approved-usecase and associated-user data-passthrough acknowledgments start unchecked and must be literal true. These user attestations never prove Xero approval or activate Live. The original actor separately decides the exact Human task; current organization AND workspace membership, account/material, node/input/policy, consumed decision, owned lease and one CAS physical claim are revalidated through persistence and fresh OUTPUT. Current provider approval, token/tenant entitlement and associated-user consent remain unverified; resolve those before actual provider activation/testing. Current Xero terms restrict approved use cases, third-party passthrough and model training/adaptation; they do not establish a blanket inference ban.

One exact contact in data and sourceItemsJson preserves bounded original business JSON, including normal prototype-shaped keys and possible personal, bank or tax information, in ordinary output/history/downstream. The raw envelope is discarded; returned URLs stay inert. Local30s/1MiB/fatalUTF8/structural bounds, zero redirects/retries and consumed receipts prevent automatic replay of uncertain attempts. Import/export/reopen retain unsupported raw intent, raw versions and credential IDs; no automatic consent or OAuth-credential alias. Invoice, list, writes, Tool/Trigger and fullnode parity remain unsupported. Real provider, DNS/TLS, Review, durable DB/restart and real human authentication remain untested.

Consent must be saved as seven literal true booleans; acknowledgment expressions are unavailable and cannot acquire consent by resolving to true. A timely settled contact can pass through a later Wait under a new trusted resume revision and current owned lease, with its original signed task/wait/decision/claim/result conserved and current authority checked again; OUTPUT never sends again. The original send approval expires after15minutes; a timely signed settled result may outlive that send window, while retries, recovery or changed checkpoint attempts refuse.

Azure Storage: first container page

Use Azure Storage → List containers (first page), operation container.getAll / tool azureStorage_container_getAll. This is an ordinary numeric n8n typeVersion 1 compatibility subset. Save an existing account in Named fields or Advanced JSON:

{
  "profile": "azureStorageManualBearerV1",
  "account": "youraccount",
  "accessToken": "YOUR_EXISTING_STORAGE_BEARER",
  "audience": "https://storage.azure.com/",
  "expiresAt": "2099-01-01T00:00:00.000Z"
}

Use the token's actual expiry; the example date is a placeholder. Account is 3–24 lowercase letters/digits, without a URL. Save/update/reopen encrypt locally, are write-only and remain unverified with zero provider HTTP. There is no Test, OAuth acquisition/refresh, SharedKey signer, SAS, discovery or Azure resource creation. Token signature/issuer/audience/expiry claims and effective rights remain unverified. List Containers permissions require Microsoft.Storage/storageAccounts/blobServices/containers/read scoped to the account or above; a blob-level entitlement alone does not prove account-list access. Tokens expiring within 30 seconds are refused at execution.

Original imports must declare exactly ordinary numeric version 1, resource:container, operation:getAll, returnAll:false, limit:1, and matching original authentication:oAuth2/azureStorageOAuth2Api or authentication:sharedKey/azureStorageSharedKeyApi. Original declarations and unsupported intent remain in the source ledger. Reselect the separate manual bearer account; no original OAuth/SharedKey authentication parity is claimed. Other defaults/options, metadata/system/deleted filters and Tool/Trigger require visible manual repair; additional admitted operations are described below.

Input requires parameterSchemaVersion:2 and four independent literal acknowledgments: migrationAcknowledged:true, rawRetentionAcknowledged:true, onePhysicalAttemptAcknowledged:true and firstPageOnlyAcknowledged:true; none is automatically checked. The original actor needs current direct organization AND workspace membership, current selected account and input revisions, WORKFLOW_LIVE_AZURE_STORAGE=true and the independent current workspace live preference. A separate signed Human Task binds the exact safe request preview without embedding the bearer. Nonempty owned lease, original task/wait/decision, checkpoint attempt and consumed resume revision remain required. One CAS claim permits one physical attempt; uncertain or used claims never resend, including fresh resumes or node retry settings.

The request is exactly GET https://{account}.blob.core.windows.net/?comp=list&maxresults=1, with Bearer authorization, a fresh UTC x-ms-date, and source x-ms-version:2021-12-02. Public DNS, admitted IP, certificate/SNI and remote peer are revalidated. For this first-container-page action, custom/private/sovereign endpoints, alternate ports, redirects, retries and continuation requests are unsupported; IPv6-only hosts remain unsupported.

A successful 200 XML response yields data.containers, data.maxResults:1 and opaque data.nextMarker. paging.completeness is partial-first-page when a marker exists, otherwise complete-first-page; this never implies full pagination. Empty pages retain their marker, fixing the original helper shortcut's loss. Unknown container fields/attributes and textual metadata (including 0007) persist in normal history and downstream mappings. Returned URLs remain inert. Root-level unknown fields are omitted as in the original helper. XML names follow source helper normalization; strict named boolean/safe integer conversion applies outside metadata. Prototype-sensitive names and normalization collisions refuse success. This differs deliberately from the original metadata coercion.

Limits: one total 30-second dispatch/read/decode deadline, 256 KiB body, depth 24, 4,096 elements/reads, one container, and an 8,192-character marker. Strict UTF-8/XML, exact response status/media/length, secret-reflection checks and bounded streaming precede success. DTD, custom/external entities, namespaces, comments, CDATA and processing instructions are rejected. The five predefined XML entities and valid numeric character references are decoded without external resolution. Raw transport text is discarded; no full XML/parser parity is claimed. Existing business data may be private and remains in ordinary history; this adds no retention/encryption guarantee for that history.

Local tests simulate provider responses, Prisma facts and native sockets. Real Azure token claims/entitlement/RBAC propagation, service responses, network ACL/private-network constraints, native deployment, actual durable database/Redis restart and organization-scoped Review/tutorial behavior remain untested.

Azure Storage and Cosmos DB: additional bounded operations

Azure Storage also exposes container.get/create/delete and blob.getAll/get/create/delete, using the same exact azureStorageManualBearerV1 account and fixed public origin. Select the operation, review its disclosure and supply schema 2 plus literal migration, retention and one-attempt consent. Container creation needs createContainerAcknowledged; container deletion needs deleteContainerAcknowledged and removes every blob. Blob upload needs replaceBlobAcknowledged, explicit UTF-8 content (at most 4 KiB) and contentType; it can replace content and metadata. Blob deletion needs deleteBlobAcknowledged; snapshots, leases and conditional requests are unsupported. Every write requires a separate exact-request Human Task and one physical claim; a lost response never authorizes retry.

blob.getAll requires firstPageOnlyAcknowledged and an explicit limit of 1–100. Optional include accepts only the fields exposed by the form. It returns data.blobs, data.maxResults and an opaque data.nextMarker; empty partial pages retain their marker and it is never followed. blob.get requires textOnlyAcknowledged and returns bounded UTF-8 data.content with name, properties and metadata. Original n8n blob downloads produce binary items and remain refused; configure this different text-only operation manually. Original blob uploads using binary or URL sources also remain refused. Container read/create/delete, bounded blob listing and deletion can migrate only their admitted literal source options. Unsupported fields remain visible for repair. XML keeps the 256 KiB/depth-24/4,096-element bounds; text download is at most 256 KiB. All calls retain the total 30-second budget.

Azure Cosmos DB also exposes container.getAll/create/delete and item.get/getAll/query/create/update/delete with the exact azureCosmosDbMasterKeyV1 account, saved database and fixed public origin. Every operation requires schema 2 and literal migration, retention and one-attempt consent; all five writes additionally require writeEffectAcknowledged. The original actor needs current organization AND workspace membership and both live gates, then confirms the exact selected account, request and body. Every action uses one HMAC-authenticated request and one physical claim; uncertainty remains unverified and never resends.

Container/item listing accepts one page with maxItemCount 1–100; continuation is opaque and never followed. Query sends one POST with explicit SQL and named parameters, not a write. Choose crossPartition (potentially higher RU charges) or singlePartition with an explicit string partition key. It accepts at most 1,000 returned values; a page may be empty or partial. Point item reads and writes need an explicit string partition key; no discovery probe or inferred key is used. Return values are data.containers, data.items, data.item, data.container or {deleted:true}, with bounded envelopes and numeric-lexeme metadata. New item/query responses preserve otherwise unsafe numeric spellings as text. The original container.get contract retains its stricter numeric refusal. Normal history and downstream mappings retain business data.

Native item creation never upserts; an existing id conflicts. Native item update replaces the whole item using the exact authored JSON and matching id; omitted properties disappear. Both differ from original n8n upsert/injected-body behavior, so those imports remain refused and require manual configuration. Container creation accepts one Hash partition path and optional indexing policy/manual throughput: 400–1,000,000 RU/s in steps of 100 can incur ongoing billing. Deleting a container removes all contents. No patch/upsert/autoscale, retries, redirects or automatic continuation is implemented. Limits remain total 30 seconds, 1 MiB response, depth 32 and 20,000 nodes; authored item/policy JSON is at most 8 KiB.

These are bounded native operations and explicit migrations, not full n8n item/authentication parity. Local HOST tests use simulated provider responses and database facts. Real provider credentials, grants, charges, native DNS/TLS, durable restart and authenticated organization Review/tutorial behavior remain untested.

Firebase Realtime Database manual token profile

firebaseRealtimeManualBearerV1 accepts exactly profile, canonical public databaseOrigin, already supplied Google OAuth accessToken, UTC ISO expiresAt and the two documented required scope metadata values. Save/update/reopen are encrypted, write-only and unverified with zero HTTP/DNS; no Test or refresh. Do not substitute a Firebase ID token, legacy secret, service-account key JSON or generic Google Workspace credential. Execution requires more than30s remaining declared token lifetime; metadata alone does not validate the token or permissions. See the example, finite regional hosts and prerequisites. Provider access, native DNS/TLS, Review and durable restart remain untested.

Explicit ordinary numeric version 1 Firebase update, push, create and delete now migrate to separate bounded native writes: PATCH, POST, PUT and DELETE respectively, using the same firebaseRealtimeManualBearerV1 account and one nonroot literal path. The omitted original default is still refused. Body operations retain the original comma-separated attributes; bind inputData explicitly to the upstream record because n8n implicitly read the current item. Only listed own top-level properties present in that record are sent, as canonical JSON (at most 4 KiB). Requests with no matching attributes, server values or multi-path keys are refused.

All writes require the three common literal acknowledgments plus externalWriteAcknowledged; PUT also needs fullReplacementAcknowledged because omitted subtree values are removed, and DELETE needs subtreeDeletionAcknowledged because it removes the entire subtree. Import leaves every consent false and does not select or acquire credentials. Review the exact account, verb, path and body in the original-actor Human Task under current organization AND workspace authority and both live gates. One durable physical claim permits one attempt; a timeout, disconnect or malformed response leaves the outcome unverified with no automatic retry or replay. Successful writes retain bounded data, rawJson and request-body byte count in ordinary history. POST returns the generated child name; DELETE returns null. These are explicit adaptations; original scalar/null/item wrapping and implicit per-item execution parity are not claimed. Real provider writes, charges and Review walkthroughs remain untested.

QuickBooks manual bill account

quickbooksBillManualBearerV1 stores exactly profile, tokenKind:"oauth2-access-token", existing accessToken, decimal-string realmId, explicit environment:"production"|"sandbox", accountingScope:"com.intuit.quickbooks.accounting" and positive safe-integer expiresAtEpochMs. The external realm is distinct from application organization/workspace. Named and Advanced JSON Save and complete same-ID Update account use encrypted, write-only storage and remain local/unverified with no provider HTTP/DNS. Reopening never reveals the saved token. Test and bulk Test are unsupported; original OAuth credentials are not converted or refreshed.

Scope, company authorization and expiry are user-supplied metadata, not token introspection. Expired metadata refuses dispatch. Saving grants no execution authority; bill reads separately require the exact selected account, literal financial-data persistence acknowledgment and original-actor Human approval. See QuickBooks fields, raw financial retention and limits. Real provider/native network, durable database/restart and Review remain untested.

Native PG manual read account

nativePgReadManualTlsV1 accepts only the explicit crateDb or timescaleDb profile, public DNS host, numeric port, ASCII database/user/password, tlsProfile:"system", matching serverName, and reviewed schema/table/column-array fields. The complete account shape is validated locally before storage. Save/update are encrypted and unverified, return masked summaries and do not connect. A complete replacement updates the same ID and invalidates prior approval. Direct Test and bulk Test are unsupported; they do not perform a provider request, DNS lookup or database connection. Existing authorization checks still apply. Actual database compatibility and authenticated Review account lifecycle remain unverified.

En español: nativePgReadManualTlsV1 exige un perfil explícito, host DNS público, puerto numérico, base de datos, usuario y contraseña ASCII, TLS del sistema con identidad del host y esquema/tabla/columnas revisados. Guardar y actualizar validan y cifran localmente sin conectar ni verificar permisos; solo devuelven un resumen enmascarado. Reemplazar conserva el ID e invalida aprobaciones anteriores. Test y Test masivo no están disponibles.

A blank Named password explicitly saves password:"", including on update; it never retains the previous password. Advanced JSON can supply the same empty string. En español: dejar vacía la contraseña guarda password:"" explícitamente, también al actualizar; nunca conserva la contraseña anterior.

Only inert id/name credential references may enter the original-source record. Embedded credential fields or inline account material are refused before original import, portable reopen or export; unsupported safe parameters and business field names are retained without a field-name blacklist. En español: el registro original solo admite referencias inertes id/name; los campos de credenciales incrustados o material de cuenta se rechazan antes de importar, reabrir o exportar. Los parámetros seguros no compatibles y los nombres de campos de negocio se conservan sin una lista de nombres prohibidos.

LDAP manual LDAPS account

nativeLdapReadManualLdapsV1 accepts only the complete manual LDAPS profile, including the exact reviewed selection. Settings and credential API create/update paths use the same local parser before encrypted persistence. Save/update return masked summaries and perform no directory/DNS access. Reopen does not disclose saved values. Updating preserves the ID and changes the keyed saved-material revision, invalidating earlier approval. Direct and bulk Test refuse locally with zero provider requests. Plaintext, StartTLS, custom trust, anonymous/SASL authentication, imported credentials and OAuth acquisition are unsupported. Existing credential ownership and authorization rules still apply; real directory permissions remain unverified.

En español: nativeLdapReadManualLdapsV1 valida el perfil LDAPS completo y la selección revisada antes de cifrar. Guardar y actualizar no hacen DNS ni contactan con el directorio; devuelven resúmenes enmascarados. Reabrir no revela secretos, actualizar conserva el ID e invalida aprobaciones, y Test directo o masivo rechaza localmente sin solicitudes al proveedor.

MySQL reviewed manual TLS account

nativeMySqlReadManualTlsV1 requires the exact MySQL 8.4 manual account shape: system TLS, matching public hostname/serverName, explicit port/database/user/password and reviewed table/columns. Create and complete replacement validate locally before encrypted storage and return write-only masked summaries, without DNS, SDK, socket, authentication or permission tests. Replacement preserves ID and invalidates earlier approvals. Direct and bulk Test are unavailable; original MySQL credentials are not converted automatically. Real account privileges and the authenticated Settings/Review lifecycle remain unverified.

En español: la cuenta manual MySQL exige el perfil exacto, TLS del sistema, host y nombre TLS iguales, puerto, base de datos, usuario, contraseña y tabla/columnas revisadas. Guardar y reemplazar valida y cifra sin conectar ni probar permisos; el resumen es enmascarado y el ID se conserva. No hay Test ni conversión automática de credenciales originales.

MongoDB manual system-TLS account

nativeMongoReadManualTlsV1 accepts the complete manual system-TLS profile. Named fields and Advanced JSON share local validation before encryption; reopen is write-only. Save/update make no DNS/connection/Test, and replacement invalidates prior approval. Read-only privileges remain unverified.

En español: La cuenta manual exige perfil completo y selección revisada. Guardar/actualizar validan y cifran localmente sin conexión ni Test; reabrir no revela secretos y reemplazar invalida aprobaciones.

Jina Reader saved manual key

jinaReaderManualKeyV1 accepts only complete serialized {apiKey} in the finite ASCII token profile. Credential create/update validates before encrypted persistence, rejects wrong-case families, aliases, arbitrary origins/headers and partial hidden-secret retention, and returns masked summaries. Replacement preserves ID and invalidates prior approval. Reopen is write-only. API/tRPC/direct/bulk Test refuses locally before secret resolution or provider requests; the original key-in-dashboard-query Test is omitted. Import ID/name references are inert. See manual fields.

Jina performs the remote target fetch; its target DNS, redirect and access-policy behavior are not local transport facts. One request can disclose the target URL and consume credits. Raw untrusted page data persists in authorized workflow history and may reach downstream AI. Provider/key compatibility, credits, deployment and authenticated Review remain untested. Fresh authority checks and guarded writes do not make database and network actions atomic.

En español: Jina obtiene el destino remoto; su DNS, redirecciones y políticas no son hechos del transporte local. Una solicitud puede revelar la URL y consumir créditos. Los datos sin confianza persisten en historial y pueden llegar a IA posterior. Compatibilidad real, créditos, despliegue y Review autenticado siguen sin probarse. Organización Y espacio, actor original y cuenta guardada vigente siguen siendo obligatorios; un intento usado o incierto no se repite.

AWS Rekognition DetectLabels (preview)

Use awsRekognitionManualSigV4V1 with profile aws-rekognition-manual-sigv4-v1, partition aws and region us-east-1. Named fields and Advanced JSON save the same encrypted, write-only, unverified account. manual-static omits session token and expiry; manual-temporary requires both. Reopening leaves keys blank; updating requires complete replacement and invalidates prior approvals. Test and bulk Test make no provider request. Saving does not validate the declared AWS account or the image.

Execution requires both the deployment setting WORKFLOW_LIVE_NATIVE_REKOGNITION=true and the workspace live preference for aws-rekognition. Human approval belongs to the original actor and binds the saved account, exact source, input and workflow version. Changes require a new approval. An uncertain paid outcome must not be replayed.

Real AWS requests and authenticated organization/workspace Review walkthroughs remain untested. Local simulated responses do not verify AWS permissions, image access or provider retention settings. See DetectLabels fields, acknowledgments and limits.

Español: DetectLabels en vista previa

Usa awsRekognitionManualSigV4V1 con perfil aws-rekognition-manual-sigv4-v1, partición aws y región us-east-1. Los campos con nombre y JSON avanzado guardan la misma cuenta cifrada, de solo escritura y sin verificar. manual-static omite token de sesión y caducidad; manual-temporary exige ambos. Al reabrir, las claves quedan vacías; actualizar exige reemplazo completo e invalida aprobaciones anteriores. Las pruebas individuales y masivas no solicitan al proveedor. Guardar no valida la cuenta AWS declarada ni la imagen.

La ejecución exige tanto WORKFLOW_LIVE_NATIVE_REKOGNITION=true en el despliegue como la preferencia de ejecución real de aws-rekognition en el workspace. La aprobación humana corresponde al actor original y vincula la cuenta guardada, el origen exacto, la entrada y la versión del flujo. Los cambios exigen una nueva aprobación. Un resultado facturable incierto no debe repetirse.

Siguen sin probarse las solicitudes reales a AWS y los recorridos autenticados de organización y workspace en Review. Las respuestas locales simuladas no verifican permisos de AWS, acceso a la imagen ni la política de retención del proveedor. Consulta los campos, confirmaciones y límites de DetectLabels.

AWS Textract AnalyzeExpense (preview)

The separate credential type is awsTextractManualSigV4V1, restricted to the aws partition and us-east-1. Save an existing manual-static or manual-temporary AWS account through the named fields or Advanced JSON. Static accounts omit sessionToken and expiresAt; temporary accounts require both a supplied token and explicit UTC expiry. Dispatch refuses temporary credentials with ninety seconds or less remaining. No STS, role assumption, refresh or discovery occurs.

Save encrypts the supplied account and returns nonsecret metadata. Secrets remain write-only: reopening leaves them blank, and updating requires a full replacement. Save is unverified and does not call AWS. Individual Test, both credentials Test API routes and bulk Test refuse this account before resolving its secret. Importing AWS ID/name references selects no account or permission. Replacing the selected account invalidates the request approval.

Execution requires both the deployment setting WORKFLOW_LIVE_NATIVE_TEXTRACT=true and the workspace live preference aws-textract. Real AWS requests and authenticated organization/workspace Review walkthroughs remain untested.

Español: AnalyzeExpense en vista previa

El tipo separado awsTextractManualSigV4V1 se limita a la partición aws y la región us-east-1. Guarda una cuenta AWS manual existente en los campos o en JSON avanzado. La cuenta estática omite sessionToken y expiresAt; la temporal exige ambos y una caducidad UTC explícita. Se rechaza ejecutar con noventa segundos o menos de vigencia. No se obtiene identidad mediante STS ni se asumen roles, renuevan claves o descubren cuentas.

Guardar cifra la cuenta y devuelve solo metadatos sin secretos. Al reabrir, las claves quedan vacías; actualizar exige reemplazarlas por completo. Guardar no verifica la identidad ni contacta AWS. Test individual, ambas rutas API de Test y Test masivo rechazan esta cuenta antes de resolver el secreto. Importar referencias AWS no selecciona cuenta ni permiso. Cambiar la cuenta exige una nueva aprobación.

Se exige tanto WORKFLOW_LIVE_NATIVE_TEXTRACT=true en el despliegue como la preferencia real aws-textract del workspace. Siguen sin probarse las solicitudes reales AWS y los recorridos autenticados de organización y workspace en Review.

Microsoft SQL manual account (storage only)

The manual Microsoft SQL credential type is exactly microsoftSqlManualTds74TlsV1, with provider microsoft-sql. Its JSON value has exactly six keys: profileId: "mssql-manual-tds74-tls-v1", host, numeric port, database, username, password. Settings Save and replacement run the authoritative account validator before encryption; Settings Update account requires the complete replacement secret. This Settings rule does not change the generic PATCH omission contract above. Credential Test returns unsupported before resolving the secret, after existing access checks; bulk Test skips this type.

Use an explicit DNS or IPv4 host, an integer port from 1 to 65535, and SQL username/password authentication. Named instances, connection URLs and Windows domain usernames are unsupported. Password spaces, tabs and Unicode remain exact; passwords containing CR or LF stay in Advanced JSON with escaped line breaks. Conversion to named fields refuses values that would change. The secret contains no account ID, ciphertext revision, reviewed selection or client authority flags.

No SQL operation or SELECT execution is available. Test and bulk Test are unavailable; Save makes no DNS, connection, SQL or schema-discovery request. The account remains unverified: server identity, database permissions, grants and row-level security have not been checked. See account setup.

Español: cuenta manual de Microsoft SQL (solo almacenamiento)

El tipo de credencial manual de Microsoft SQL es exactamente microsoftSqlManualTds74TlsV1, con proveedor microsoft-sql. Su valor JSON contiene exactamente seis claves: profileId: "mssql-manual-tds74-tls-v1", host, port numérico, database, username, password. Guardar y reemplazar desde Configuración ejecutan el validador autoritativo de la cuenta antes del cifrado; Actualizar cuenta exige el secreto completo de reemplazo. Esta regla de Configuración no cambia el contrato genérico de omisión de PATCH explicado arriba. Test devuelve un resultado no admitido antes de resolver el secreto, tras los controles de acceso existentes; Test masivo omite este tipo.

Usa un host DNS o IPv4 explícito, un puerto entero de 1 a 65535 y autenticación SQL con usuario y contraseña. No se admiten instancias con nombre, URL de conexión ni usuarios de dominio de Windows. Los espacios, las tabulaciones y Unicode de la contraseña permanecen exactos; las contraseñas con CR o LF quedan en JSON avanzado con los saltos de línea escapados. La conversión a campos rechaza valores que cambiarían. El secreto no contiene ID de cuenta, revisión del texto cifrado, selección revisada ni indicadores de autoridad del cliente.

No hay operaciones SQL ni ejecución de SELECT disponibles. Test y Test masivo no están disponibles; guardar no hace solicitudes de DNS, conexión, SQL ni descubrimiento de esquemas. La cuenta permanece sin verificar: no se han comprobado la identidad del servidor, los permisos de base de datos, las concesiones ni la seguridad por filas. Consulta la configuración de la cuenta.

Google directory complete-record reads

The additive Chat spaces.getRaw and Contacts contacts.getRaw operations reuse exactly googleChatManualBearerApi and googleContactsManualBearerApi, respectively, with only accessToken. Reselect a current manual account after import; historical OAuth/service-account references stay inert and are never converted. Save remains local/unverified and Test is unavailable. A separate initially unchecked full-record retention acknowledgment is required in addition to independent execution confirmation, because private contact and space records enter ordinary workflow history and downstream data. See the bounded getter contracts.