Integrations

Endpoints for integrations under /api/v1/integrations. Any valid bearer API key is accepted (not limited to workspace scope). Session twins: GET|PATCH /api/integrations. Product behavior: Integrations and credentials.

Endpoints

OAuth start/callback are session-only (GET /api/integrations/oauth/start, /api/integrations/oauth/callback). They are not under /api/v1.

OAuth start can return 403 with step_up_required, mfa_enrollment_required, or mfa_challenge_required. The Integrations screen opens its MFA dialog, preserving the workspace, page and selected credential name. Successful verification retries OAuth start once and then opens the returned provider URL. Canceling does not retry. Another refusal appears inside the integration card; verification does not override Google release policy or provider consent.

In production, FLUXUS_GOOGLE_OAUTH_RELEASE_POLICY must register the selected Google Client ID. Each registration defaults to connectionAccess: "all-users"; "verification-only" explicitly requires approved scopes or an exact verification audience. Client registration and access do not certify Google approval. Missing, malformed, duplicate or unregistered client policies still refuse consent.

Google consent accepts googlePurpose=standard|agent (default standard). The server signs that purpose and Client ID into its HttpOnly-cookie-bound state and rechecks them at callback. Agent consent produces a separate personal credential instead of overwriting a traditional integration.

For Workspace MCP, use key=google-mcp-{service}-{read|write} and the prepared mcpServerId; both must match the service/access stored in that workspace. These keys always use the agent client. The existing callback is reused, saves the new grant, binds it to the MCP connection and performs discovery. Google client classification, connection access and Workspace policy are independent checks. There is no is_agentic request parameter: classification is configured in Google Cloud.

List integrations

GET /api/v1/integrations returns { integrations[] } — catalog rows for the API key workspace, including status (available | connected), credential pointers, and connectedCredentials[].

401 { "error": "Valid bearer API key is required" } without a token. Unknown integration key on PATCH: 400.

Connect or toggle

PATCH /api/v1/integrations connects, disconnects, or attaches a credential:

When connected is true and a credentialValue is supplied, the integration is connected with a new or updated workspace credential and the response is { integration, credential } (maskedValue only). Otherwise the call upserts the connection flag and returns { integration }. Multiple named credentials can share one key.

Next steps

Home Assistant uses a selected native homeAssistantApi account, not OAuth or generic HTTP credentials. Its five bounded reads require an enabled workspace live control, initially unchecked personal-data acknowledgment and separate invocation confirmation. See setup and limits.

Humantic AI uses a selected native humanticAiApi account and its own workspace live control. Profile creation starts processing despite using GET; metadata retrieval may consume credits and receives personal data before projection. Both need initially unchecked acknowledgments and separate invocation confirmation. See setup and limits.

Iterable adds six bounded events, user and list operations with selected native iterableApi accounts and an explicit workspace live control. Region fixes the endpoint. Personal-data and write-effect acknowledgments start unchecked; global channel unsubscription needs an extra acknowledgment. See setup and limits.

HighLevel adds seventeen bounded legacy contact, task, opportunity and calendar operations using a selected native highLevelPitApi account and explicit workspace live control. Personal-data and write-effect switches start unchecked and require separate invocation confirmation; upsert has an additional existing-contact acknowledgment. See setup and limits.

Keap exposes29 bounded actions: twelve reads and seventeen writes across companies, contacts, notes, tags, orders, products, email records and files. Select the saved personal-access-token account, enable workspace live execution, review personal-data and applicable effect acknowledgments, then confirm separately. Lists use explicit filters and limits. Contact upsert may merge; order/product writes can affect finances, queued email does not prove delivery, and file upload requires explicit visibility. Indeterminate writes require inspection before manual retry. See Keap setup.

Invoice Ninja exposes 31 finite hosted-v5 reads, creates, deletes, payment matching and email requests with the selected native invoiceNinjaV5Api account. Enable the workspace live control, review initially unchecked privacy/effect switches and confirm each invocation separately. Lists are partial single pages; financial decimal inputs remain strings and email delivery is unverified. See supported operations and limits.

LinkedIn exposes three confirmed publication actions: literal text, article metadata and an existing image URN. Select a saved linkedInAccessTokenApi account, enable workspace live execution, review author/visibility/content and personal data, check the initially unchecked publication acknowledgment and confirm separately. Responses project only the exact header URN; uncertain attempts must not be retried automatically. No upload, readback, OAuth issuance or n8n conversion is included. See LinkedIn setup.

Mandrill exposes two confirmed Transactional sends: HTML and an existing template slug. Select the saved native account, enable workspace live execution and review the three initially unchecked privacy/email/charge acknowledgments before confirming independently. Selected recipient statuses and actual IDs are not delivery proof; an indeterminate attempt is not retried automatically. See Mandrill fields and limits.

LingvaNex exposes List languages and Translate text with explicit usage/disclosure/charge acknowledgments and separate confirmation. Magento exposes six bounded reads and nine explicitly confirmed account/catalog/financial/fulfillment effects using a selected merchant token. Every operation makes one attempt; indeterminate translation charges or Magento writes require inspection before an intentional repeat. No complete language catalog, full merchant export or remote success is inferred. See LingvaNex limits and Magento limits.

The six finite native profiles add47 operations: Home Assistant actions9, Matrix9, Mailcheck1, Monica25 including reminders5, Mindee InvoiceV4 processing1 and MessageBird2. Select the exact saved account and workspace live control; initially unchecked applicable policies and independent confirmation are required. Results are bounded received projections and do not prove effects, delivery, charges, complete data or rights. All operations make one attempt. See fields, privacy and limits.

ReceiptV5 adds one document action, Monica adds five Calls actions (30 total), and Mocean adds SMS/voice sends. Together with the preceding47 this is55 finite operations across eight account profiles. Exact selected accounts, workspace live controls, initially unchecked applicable acknowledgments and separate confirmation remain required. Every invocation makes one attempt. Received IDs and projections do not prove delivery, charges, complete data or durability. See fields and limits.

Mistral PDF OCR1 plus Microsoft Teams Graph v1 reads8 bring the preceding55 group to64 operations across ten native profiles. These are partial ordinary/Tool service subsets with no import conversion, chat/embedding model, Teams write/trigger or send-and-wait support. Each invocation needs its exact saved native account, workspace control, initially unchecked applicable acknowledgments and separate confirmation. See fields, routes and projections.

The next14 finite actions add Monica activities.get/page/create/replace/delete and nine Teams channel/message/Planner mutations. The previous64 group becomes78 actions across the same ten profiles, with partial service coverage and no import aliases. All prior read subsets remain available; HTTP204 observes only status and uncertain mutations are not retried. See the fourteen field and response contracts.

Perplexity Agent fast and OpenThesaurus German synonym lookup add two finite actions, extending the preceding78 group to80. Perplexity is a distinct paid Agent operation, without Sonar/import compatibility. OpenThesaurus is the single exact no-auth public operation and requires no configured account. Both require applicable unchecked disclosure/charge acknowledgments, separate confirmation and workspace live enablement; no automatic n8n alias is added. See the two field, response and privacy contracts.

Twelve Outlook token reads plus Monica conversations6/contacts5 extend the preceding80-action group to103 finite actions. Monica has46 actions. Outlook token reads are distinct from the legacy OAuth subset. These partial ordinary/Tool services have no automatic n8n import aliases or credential conversion. See the23 field and response contracts.

Sixteen further writes extend that103-action group to119; Outlook Graph v1 token now has28 finite operations and Monica remains46. Calendar/contact/folder/event create/update/delete and draft create/update/delete/send use the existing native account/control, exact selected context, initially unchecked applicable policies and separate confirmation. Draft send202 is acceptance only, and message deletion is not draft-only. Ordinary and Tool coverage remains partial, without OAuth conversion, import aliases or full n8n parity. See the sixteen write contracts.

urlscan private submission/result2 and Marketstack v2 selected reads3 extend the preceding119-action group to124. These ordinary/Tool services remain partial, without automatic n8n import aliases, historical credential conversion, polling or full parity. The exact native urlscanV1Api/marketstackV2Api accounts, workspace controls and operation-specific acknowledgment/confirmation policies apply. See the five routes and projections.

npm public registry

Four public metadata reads extend the preceding124-action group to128: package.version-get, package.versions-list, package.dist-tags-list and packages.search-page. Authentication is none, with independent confirmation and an exact native account-free path. Ordinary npm/npm Tool remain partial service coverage with zero import aliases, not full n8n parity. See the npm field, response, privacy and timing contract.

Zulip and Google Books selected metadata

Five selected reads extend the preceding 128-action group to 133: Zulip users.get, users.me and channels.get, plus Google Books volumes.get and volumes.search. Both ordinary and Tool reference services remain partial, with zero automatic import aliases or historical credential conversion. Use the exact selected native account, initially unchecked disclosure controls and independent confirmation. See the fields and bounded response contract.

Google BigQuery and Business Profile selected metadata operations

Four operations extend the preceding 141-action group to 145: BigQuery tables.get and datasets.listPage, plus Business Profile locations.get and locations.listPage. Get uses the exact saved Business Profile location with empty input {}; list uses its configured account. Select the matching native manual account and review independent execution confirmation. IDs remain strings, page sizes are actual integers 1–100, and table/token whitespace is preserved. Explicit workspace booleans override environment defaults; without an override only exact false disables, and an absent flag enables. One attempt/page, no SQL/jobs/table data, reviews/posts, writes, OAuth lifecycle or automatic paging. Service coverage is partial, with zero n8n aliases or action/field parity; project eligibility and real provider behavior remain unverified. See full fields, projections and limits.

Google Chat, Storage and Natural Language selected operations

Five finite operations extend the preceding 136-action group to 141: Chat spaces.get/spaces.listPage, Cloud Storage buckets.getMetadata/objects.listPage and Natural Language analyzeSentiment. Select each exact manual account and live control. Independent confirmation applies to all five; sentiment additionally requires two initially unchecked disclosure/billing choices. Metadata pages never establish completeness; Storage integers and sentiment numeric tokens remain strings. Ordinary/Tool coverage is partial, with no n8n import aliases. See fields, projections and limits.

Google Translate and Contacts selected operations

Translate plain text and Contacts get/listPage add three finite operations, extending the preceding 133-action group to 136. Exact selected manual bearer accounts and workspace live controls apply. Translation requires separate initially unchecked disclosure/billing choices and independent confirmation; Contacts reads require independent confirmation without an acknowledgment input. One attempt, no automatic paging, OAuth conversion or import aliases. Text and contact results can enter retained workflow history. Ordinary and Tool services remain partial. See fields, routes and limits.

Microsoft OneDrive and SharePoint selected metadata operations

Four selected Microsoft Graph reads extend the preceding 145-action group to 149: OneDrive items.getMetadata and items.childrenPage, plus SharePoint site.get and lists.firstPage. Use the exact saved manual account; drive/site selection is outside operation input. Independent confirmation applies without an acknowledgment field. Explicit workspace booleans override environment defaults; otherwise only exact false disables and an absent flag enables. Both pages require explicit numeric integer pageSize 1–100, return only the first page, discard nextLink and have no continuation input. Inputs and selected results may persist; a false next-page flag proves no completeness. Ordinary/Tool service coverage is partial with zero import aliases or action/field parity. Shipped SharePoint uses REST; native site.get is a new Graph operation. See full account, input and projection contracts.

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 selected reads

The joined registry contains 2,075 tools, 2,114 operations and 172 providers. The six Graph Security and Directory reads are two microsoft-graph-security control-profile operations (secureScoreControlProfiles.getMetadata with {id}, secureScoreControlProfiles.firstPage with {pageSize}) and four google-workspace-directory operations (users.getMetadata with {userId}, groups.getMetadata with {groupId}, users.firstPage and groups.firstPage with {pageSize}). Page size is an explicit numeric integer 1–100. Every first page has inventoryComplete:false and only hasNext; continuation is neither returned nor followed.

Graph IDs use only the exact 1–256 ASCII letter/digit/underscore/hyphen subset; Directory IDs use 1–128. Case and leading zeros remain exact. Directory's required saved customerId is outside operation input; no email/domain/URL/my_customer customer alias or silent whitespace trimming. Returned users must match that customer, while group ownership cannot be independently verified because group responses have no customer field. Group directMembersCount remains quoted 1–19 digits within signed int64, preserving zero and leading zeros. Graph has no $select; full upstream profiles arrive before local projection, under a decoded 1 MiB body bound rather than a raw-wire guarantee.

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.

The controls are WORKFLOW_LIVE_MICROSOFT_GRAPH_SECURITY_MANUAL_BEARER and WORKFLOW_LIVE_GOOGLE_WORKSPACE_DIRECTORY_MANUAL_BEARER. Explicit workspace booleans override the environment; otherwise only exact false disables and an absent flag enables. The original n8n microsoftGraphSecurity and gSuiteAdmin ordinary/Tool inventory rows receive partial service coverage only: no import aliases, secure-score parity, wider user/group/device management, OAuth or full action/field parity. The 811-row ledger now has 309 partial, 487 unassessed and 15 service-only unimplemented-trigger rows. See credentials, Graph contract and Directory contract.

Webex, SecurityScorecard and Wise selected reads

The joined registry adds six operations and three distinct providers: Webex webex-meeting-metadata (meetings.getMetadata, meetings.firstPage), SecurityScorecard securityscorecard-read (companies.getScorecard, companies.getFactors) and Wise wise-profile-read (profiles.list, profiles.get). These are selected read profiles, not full n8n nodes, OAuth lifecycle implementations or credential/import aliases. Ordinary Webex/SecurityScorecard and their existing Tool inventory rows, plus ordinary Wise, record partial service coverage only; there is no Wise Tool row to materialize.

Each operation requires the exact saved credential type, independent per-run confirmation and current selected-account authority. Save is local/unverified with zero provider HTTP; Test is unavailable. Credential disclosures do not replace confirmation and no operation acknowledgment field is added. Inputs and selected outputs follow ordinary history/downstream retention; full bounded upstream private fields enter adapter memory before projection. Current rights, expiry, quota, eligibility and live compatibility remain unknown. Explicit workspace booleans override environment values; otherwise only exact false disables and unset enables.

Webex uses an exact 1–512 ASCII letters/digits/underscore/hyphen meeting ID, or one explicit numeric page size 1–100 and a positive calendar-valid UTC-seconds range at most 31 days. Get leaves current=false; List leaves current=true and meetingSeries defaults. continuationPresent is only nonempty Link-header presence, never parsed next-page proof; links are neither returned nor followed and inventory is incomplete. See Webex inputs and output.

SecurityScorecard accepts only strict lower-case ASCII DNS company domains, not URLs or custom IDs. Existing scored-company/portfolio access is required; 403/404 is terminal without create/enroll/upgrade. Summary score is optional while domain/name/grade are required. Factor score/grade and derived issueCount preserve absence; null selected values refuse the response. See factor bounds and projections.

Wise uses fixed api.wise.com/2026Q4, with no legacy v1 fallback. Get requires positive canonical int64 decimal text through 9223372036854775807, including exact IDs above 2^53; no leading zeros or input numbers. List accepts exactly {}, reads a bare array of at most 100 entries, preserves order and duplicates and reports incomplete inventory. Only id/type/optional currentState survive, with absence distinct from null. No financial actions are available. See Wise inputs and projections and account fields.

Travis CI and Tapfiliate selected metadata

Two distinct native providers expose four selected reads:

Travis CI uses a hosted .com v3 manual token and one build or first current-user page at offset 0, limit 1–100/default 25. Tapfiliate uses a user API key for one advertiser account and one program affiliate or page 1, documented service default 25/local cap 100; it has no page-size input. Both return only selected metadata in item or items, with inventoryComplete:false. Save is local and unverified with zero provider HTTP; Test is unavailable. Existing credential disclosures remain separate from required independent per-run confirmation. Provider-level default confirmation does not override that operation requirement.

The exact inventory references n8n-nodes-base.travisCi, n8n-nodes-base.travisCiTool, n8n-nodes-base.tapfiliate and n8n-nodes-base.tapfiliateTool have partial service coverage only. Travis original get/getAll remain narrow partial subsets; cancel/restart/trigger are unported. Tapfiliate's full 12-action matrix remains partial: affiliate create/delete/get/getAll, affiliateMetadata add/remove/update, and programAffiliate add/approve/disapprove/get/getAll. Analogous metadata reads do not provide full outputs, filters, writes, pagination, original action/import aliases, credential conversion or automatic Tool wrappers.

Use workspace credentials for ordinary workflows. Organization credentials are unsupported; direct workspace membership, organization membership and execute authority are required even in organization-visible workspaces. Each operation makes one GET attempt without retries, polling or followed URLs. Full bounded private bodies enter memory before projection; ordinary input/result/history/downstream retention applies. Access, key rights, expiry, eligibility, remaining quota and charges remain unverified. See accounts, block fields and request bounds.

Onfleet, Storyblok and PostHog selected metadata

The joined registry exposes onfleet-teams-metadata, storyblok-published-eu and posthog-projects-metadata, with two native reads each. Onfleet provides teams.getMetadata and teams.listSnapshot; Storyblok provides stories.getMetadata and stories.listPage; PostHog provides projects.getMetadata and projects.listPage. All six require independent per-run confirmation, separate from credential disclosures. Provider-level confirmation metadata does not remove that operation requirement.

These use distinct existing manual credential profiles. Save and reopening send zero provider HTTP, leave credentials unverified and provide no Test. Use workspace credentials for ordinary workflows. Organization-scoped credentials are unsupported. Executing in an organization-visible workspace still requires direct workspace membership, organization membership and execute authority.

Every output reports inventoryComplete:false. Storyblok is fixed to EU published CDN v2 and page 1; PostHog uses explicit saved us/eu and organization with offset 0. Their numeric limits default to 25 and stop at 25. Onfleet's single snapshot refuses more than 100 unique teams. None automatically follows links, retries, fetches further pages or writes. Full bounded private responses enter memory before projection, and ordinary input/result/history/downstream retention applies. A GET may consume quota; rights, eligibility and charges remain unverified.

The six exact original inventory identities n8n-nodes-base.onfleet, onfleetTool, storyblok, storyblokTool, postHog and postHogTool now record partial service coverage; the short names in that list retain the same n8n-nodes-base. prefix and case. onfleetTrigger stays unassessed. Onfleet original actions and Storyblok content actions remain partial; Storyblok management actions remain unported. All five original PostHog writes (alias.create, event.create, identity.create, track.page, track.screen) remain unported. Metadata reads do not materialize old actions, import aliases or Tool wrappers, or certify compatibility. Unassessed inventory rows are not a count of missing services.

See required accounts, exact block inputs, and the provider contracts and live controls.

Paddle Billing metadata and Plivo SMS

Paddle Billing provides two product metadata reads only. All nine active original n8n Paddle Classic actions remain unported: coupon create/list/update, payment list/reschedule, plan get/list, product list and user list. Billing is a distinct API, credential profile, data set and ID system. No prices, payments, subscriptions, transactions, importer aliases or full Classic parity are provided.

Plivo sends one SMS request as an external write with possible segment and carrier charges. A local HTTP 202 result means queued, with deliveryVerified:false; it does not prove delivery. Map original n8n message manually to text; there is no importer alias. MMS, calls, multiple recipients and optional parameters remain unported. After invocation, failure, timeout or abort leaves the remote effect uncertain: do not automatically repeat the send. Check Plivo separately before deciding to send again; there is no automatic readback, callback or retry.

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. See credential fields and exact inputs and output. Inventory rows describe static service coverage, not original operation parity, import conversion or verified provider access.

ProfitWell Metrics and Peekalink Preview

ProfitWell Metrics (profitwell-metrics) provides four independently confirmed reads: company.getSettings, metric.getDaily, metric.getMonthly and plans.list. Existing private tokens use raw Authorization. Settings select locally required company strings; current primary documentation supplies no response schema or example, so these field types are local support policy. Daily series preserve each metric's own dates. Monthly history is validated in full before selecting the newest months locally. Financial number spellings remain strings without rounding. Plans are an explicit read replacing the original hidden options loader; no loader runs while saving or editing.

Peekalink Preview (peekalink-preview) provides one independently confirmed link.preview POST using an existing current Bearer key. Previewing causes external fetching, redirects, caching/media storage and possible quota or billing use. Local public HTTPS checks do not validate DNS or guarantee provider redirect safety. Selected metadata is returned; no returned image, HTML or other media is fetched or rendered. HTTP 200 with ok:false is a failure. After invocation any failure leaves processing or billing uncertain: do not automatically retry. Original isAvailable has no established current primary contract and remains unported; preview ok is not a substitute.

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 fields and limits. The four original ordinary/Tool inventory rows record partial service coverage only, with four and one operations respectively and zero import aliases.

Phantombuster agent metadata and explicit write requests

The public Phantombuster provider (phantombuster-agent-metadata) exposes five independently confirmed operation labels, literally agent.getMetadata, agent.listMetadata, agent.getOutputMetadata, agent.launchRequest and agent.deleteRequest.

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.

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.

Only the list result has inventoryComplete:false and selection:"local-prefix". These flags are not added to get, output-metadata or write results. Original item loops, raw logs/results, resolveData, returnAll, hidden option loaders, import aliases and automatic Tool materialization are unsupported. The two original ordinary/Tool inventory rows describe this same partial subset, with five operations and zero aliases; they do not establish full parity.

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 fields and output schemas and credential JSON.

Pushcut and SIGNL4 finite actions

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.

Devices has a multiselect descriptor but no static enum or option loader: the mounted field is a JSON-array text input with an Expression toggle, not a checkbox list.

Pushcut notification names are one encoded path segment, locally at most 256 code units and UTF-8 bytes, excluding control characters, slash, backslash, question mark, hash, percent and dot/dot-dot names. Devices allows at most 100 unique nonempty strings of at most 256 code units and bytes each. Omitted devices uses the vendor all-devices default. Explicit [] is sent unchanged and never guarantees no recipients. Optional input/text/title preserve empty strings and whitespace and are sent only when present; input/text are locally capped at 8192 and title at 1024 code units and UTF-8 bytes. There are no hidden defaults or substituted values. Reads validate the whole bounded array of at most 500 objects; they do not load options, paginate or promise complete inventory.

SIGNL4 message is required but may be empty when title is nonempty. Message/title/service/externalId have local maxima 8192/1024/256/512 code units and UTF-8 bytes. Optional empty title, service and externalId are accepted in the form but omitted from the wire. Service uses X-S4-Service, not old service; no X-S4-SourceSystem:n8n is added. Alerting Scenario permits exactly single_ack or multi_ack; omission leaves the team default. Filtering true sends X-S4-Filtering:true; false and absence omit it, preserving team suppression rather than forcing false. Both the select and switch expose an Expression toggle requiring an allowed string or boolean. Descriptor expression:false does not remove that mounted toggle. Text/textarea controls accept expressions; expressions must preserve the required value type.

Location accepts a typed object with exactly string latitude and longitude, through JSON text or a whole expression returning that object. Coordinates are canonical decimal strings, at most 32 code units/bytes, within latitude ±90 and longitude ±180; numbers and extra keys are refused. Binary Property accepts 1–128 ASCII letters, digits, underscores or hyphens and names the upstream persisted workspace-file descriptor; it does not accept bytes. Resolve externalId is a nonempty exact string up to 512 code units/bytes and is never replaced with eventId. No numeric parameter is introduced by these operations.

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.

The ordinary Pushcut/Pushcut Tool rows cover three partial operations each; SIGNL4/SIGNL4 Tool cover two each, with zero import aliases. These node-service rows are not operation-parity counts or automatic Tool materialization. Original multi-item behavior, Tool/import/raw-output parity and the durable Pushcut trigger callback remain unresolved. The trigger inventory row is unchanged.

See credential JSON.

seven and MSG91 message requests

Use the exact saved workspace account for seven (sms77Api with apiKey) or MSG91 (existing template SMS) (msg91Api with authkey). Save is local, zero provider HTTP and unverified; Test is unsupported. Each operation independently requires confirmation and makes one attempt without retry, redirect, fallback, polling or readback, including when outer maxTries:3 is configured.

Text and textarea controls accept whole expressions preserving their required value types. The two MSG91 selects also expose an Expression toggle despite descriptor expression:false; expressions must return strings, not numbers. Recipients is an actual textarea, not a multiselect or comma-separated fallback. Untouched optional controls remain absent in saved config. There is no hidden option loader or implicit item loop.

seven fields and defaults

To is a comma-separated string of up to 100 nonempty submitted number/contact/group entries, at most 2048 code units and UTF-8 bytes, without tabs or line breaks. This is not a cap on actual recipients: groups may fan out. From, when supplied, is empty or at most 16 numeric or 11 ASCII alphanumeric characters; verified voice senders/booked numbers and carrier caller-ID rules still apply. SMS From omitted from config is sent as an empty string; voice options.from is sent only when supplied. Explicit empty strings remain valid where specified.

SMS Message is locally limited to 1520 Unicode scalars and 6080 code units/UTF-8 bytes. Voice text is limited to 8192 code units and UTF-8 bytes. The Options textarea accepts a JSON object or a whole expression returning that object. It is not a collection of separate date, number or switch controls:

{
  "delay": "2027-01-01T00:00:00Z",
  "foreign_id": "case_A",
  "flash": false,
  "label": "",
  "performance_tracking": false,
  "ttl": 2880
}

The six SMS keys are exactly delay, foreign_id, flash, label, performance_tracking and ttl. Booleans must be JSON booleans; explicit false is sent as string 0, true as string 1, and omission stays omitted. Foreign ID and label allow empty strings or ASCII letters/digits/._@-, with local lengths 64 and 100. TTL is a JSON integer in local range 1–10080 minutes; omission leaves the documented vendor default 2880, without injecting that default into config. The original UI used empty delay/IDs/label, false booleans, TTL 2880 and an empty options object; those per-option defaults are not automatically added here. Tracking enables link shortening and needs a custom domain configured in seven; encoding, segments and group fan-out affect charges.

Delay must be a valid whole-second timezone-bearing date such as 2027-01-01T00:00:00Z, explicitly converted to Unix seconds (1798761600 for that example). Fractional seconds, impossible dates, ambiguous local time and empty delay are refused. This intentionally differs from the original raw date forwarding. Omitting delay is valid; an empty string is not omission. Voice options supports only {"from":""} or an allowed sender, with no inserted default.

Voice supports plain text or the local closed grammar voice(name), prosody(rate), self-closing break(time or strength), p, s and say-as(interpret-as). For example: <voice name="en-gb-female"><p>Hello</p><break time="500ms"/></voice>. This is not general SSML: remote audio, DTMF callback markup, loops, call control and other XML/SSML are refused. Existing vendor account webhooks and recipient keypress events may still operate. Caller ID, voice availability and live acceptance remain unverified.

MSG91 explicit existing-template migration

The original action took free-form from, to and message; this operation requires a preexisting approved template and exact variable names. There is no free-form fallback, message-to-template conversion, creation or discovery. Template Id uses 1–128 ASCII letters, digits, underscores or hyphens. Enter Recipients as strict JSON:

[{ "mobiles": "4917612345678", "OrderCode": "SYNTHETIC_A" }]

The local bounds are 1–100 objects, each with mobiles as a 6–15 digit international string starting with a nonzero digit and 0–32 case-sensitive string variables. OrderCode and orderCode differ. Variable names start with an ASCII letter and contain at most 64 ASCII letters/digits/underscores; reserved prototype names are refused. Values preserve whitespace and empty strings, with a 2048 code-unit/UTF-8-byte limit each. Numbers and comma-separated recipient text are refused. The whole JSON request is locally limited to 32768 UTF-8 bytes.

Short Url permits string 0 (off) or 1 (on); untouched config omits the key and schema validation supplies the local string 0 default. Short Url Expiry is absent unless supplied as a positive decimal string from 1 to 604800 seconds, without leading zeros; explicit empty string is invalid. Real Time Response is absent unless supplied as string 1 only. Its select has one value and no default; numeric 1, string 0 and empty expression results are invalid. Clearing an optional literal field omits it at form conversion; a whole expression returning an empty string preserves that type and is then refused. The retained official example calls expiry/realTimeResponse optional while CLI metadata calls them required; local omission follows the example and actual account compatibility remains unknown. Neither realtime response nor HTTP 200 proves delivery. URL shortening may track links.

Confirmation, output and retained data

All three writes need independent confirmation of the exact request and selected current workspace account. Saving grants no authority. Direct workspace and organization membership, execute permission, account revision, prepared identity and current live/cancel state are checked before invocation. Organization-stored credentials are unsupported; target-bound personal execution is untested. WORKFLOW_LIVE_SEVEN and WORKFLOW_LIVE_MSG91 use explicit workspace booleans before environment values; otherwise exact false disables and unset enables. No extra acknowledgment or billing-consent control is introduced.

seven uses fixed-origin POST forms with raw X-Api-Key and Accept: application/json; MSG91 uses JSON POST flow with raw authkey header. seven string 100 plus validated receipts means accepted only; 101 may be partial. MSG91 HTTP 200 with type success yields only the selected request ID and acceptance envelope. Neither output certifies delivery, cost, recipient count or template approval. Every post-invocation failure is uncertain; do not automatically repeat. There is no delivery polling, hidden retry or readback.

The native 10-second budget starts before preparation, excluding outer database and independent-confirmation latency. Response bounds are 256 KiB decoded exposed bytes, 8192 reads including completion, JSON depth 16 and 10000 nodes; overflow refuses rather than truncates. These are not wire, decompression, allocation or operating-system limits. Full bounded private responses enter memory before scanning and projection. Billing, echoed content and recipient details are omitted from selected receipts, but ordinary inputs, selected outputs, history and downstream data may be retained. Known-secret scanning does not recognize every nested, mixed or encrypted encoding.

Static shipped intent, retained current documentation and local synthetic tests do not establish real-provider acceptance, delivery, rights, costs, Review behavior or independent human confirmation. All retained REA unknowns remain unresolved. The four ordinary/Tool inventory rows are partial service mappings with zero import aliases; they do not materialize Tool wrappers or provide original item-loop, raw-output, continueOnFail, legacy free-form or general-SSML parity.

YOURLS and QuickChart finite operations

The native YOURLS provider exposes shorten / yourls_shorten, expand / yourls_expand and stats / yourls_stats. QuickChart exposes only render / quickchart_render, with no credentials. All four operations have required effective confirmation. They have no import aliases or automatically materialized Tool wrappers; native n8n item-loop, raw-output and continueOnFail parity are not claimed.

YOURLS sends a fresh POST form to the validated installation/subdirectory's yourls-api.php. The signature stays out of the URL. Shorten accepts required url and optional additionalFields with only keyword and title strings:

{ "url": "https://example.org/report", "additionalFields": { "keyword": "report", "title": "Quarterly report" } }

Omitted additional fields differ from explicit empty strings; an omitted title may cause YOURLS to fetch the target title using its own network. Shorten returns accepted:true,outcomeVerified:false,shorturl with optional selected url metadata; this can reuse an existing link and never proves new persistence. Expand and stats accept exactly {"shortUrl":"https://links.example.org/report"}. Expand returns required longurl and optional keyword/shorturl/title. Stats returns selected shorturl/url/title/timestamp/clicks; clicks is an integer lexeme string. IP/plugin fields are omitted. Returned URLs are metadata and are never followed.

Public transport requires every A/AAAA address to be public on two matching resolutions. Approved addresses are bound to the TLS connection with the original hostname, SNI and certificate verification, without environment proxy/allowlist bypasses, redirects or retries. Synthetic DNS and socket dependencies test local decisions; they do not prove real DNS/TLS. Database authority checks and socket initiation are not atomic.

QuickChart sends only fixed POST https://quickchart.io/chart, pins Chart.js major 2 and requires actual PNG, PDF, SVG or WebP bytes rather than a URL substitute. Its input is an explicit normalized items batch, not an adapter that runs original n8n items. First-item labels/options/output become the top-level fields; the last effective item type controls the chart type. Each dataset's chartOptions.horizontal overrides the top-level first-options fallback. Supported types are bar, doughnut, line, pie and polarArea.

{
  "items": [
    { "chartType": "bar", "data": [10, 20], "datasetOptions": { "label": "Sales", "backgroundColor": "#336699" } }
  ],
  "labelsMode": "array",
  "labelsArray": ["Q1", "Q2"],
  "output": "data",
  "chartOptions": { "width": 500, "height": 300, "devicePixelRatio": 2, "format": "png", "horizontal": false }
}

There are 1–50 datasets and 1–250 points per dataset. Labels support the manual labelsUi object or a direct array/strict JSON text; numeric JSON text must preserve its exact lexeme. Dataset options allow label, backgroundColor, borderColor, fill and pointStyle. Chart options allow backgroundColor, ratio1/2, dimensions1–2000, format and horizontal. Defaults are bar, manually, output data, 500×300, ratio2, PNG and horizontal false; dataset labels fall back to Chart. Declared JSON only: no JavaScript functions, plugins, remote resources or arbitrary rich configuration. These local limits are separate from vendor quotas, cost and rendering.

The output has json.chart, binary[output] and outcomeVerified:false. Each binary entry contains reference, mimeType, format, size and sha256; it represents actual bounded bytes. The trusted write-only WorkspaceFileService path creates/uploads/completes/scans/adds a typed run reference and compensates owned files/references on failure. Exact admitted run IDs include CUIDs. Current workspace AND organization, execute, actor, live, run ownership, workflow identity and cancellation are checked around asynchronous work. One file is bounded to1 MiB; an aggregate workspace quota is not available or claimed. Files are attachments, with ordinary file/history/downstream retention and scanner rules.

The native10s budget starts before preparation, excluding outer database and human-confirmation latency. JSON is bounded to256 KiB, depth16/10000 nodes and8192 reads; images have a separate 1 MiB cap and raster4M-pixel limit. Restricted local PNG/WebP decoding and SVG/PDF profiles are not full viewer/renderer conformance or wire/OS/allocation guarantees. Full bodies enter memory. Local PostgreSQL tests cover current workspace/organization authority and revocation with synthetic guarded HTTP responses; QuickChart attachment storage remains an in-memory fixture in those tests. Real provider requests, DNS/TLS, MinIO/S3, ClamAV, human approval, AI request phrasing through persistence and hosted Review remain unverified.

Vero and Vonage catalog entries

The public catalog exposes vero and vonage; their exact native credentials are veroApi {authToken} and vonageApi {apiKey,apiSecret}. List/PATCH integration configuration is separate from credential storage and per-run authority. Named fields, Advanced and Format validate strict JSON locally. Save performs zero HTTP and remains unverified; Test is unsupported. There is no OAuth or extra acknowledgment field for either provider.

Vero exposes eight explicit user/event actions: create/update, alias, unsubscribe, resubscribe, delete, addTags, removeTags and track. Alias may merge identities, delete permanently removes properties and activities, unsubscribe/resubscribe are global, and events may trigger campaigns. Vonage exposes one fixed SMS send for text, Unicode or literal binary hex plus UDH. Binary SMS is not a workspace file. The block reference records all action fields, original defaults, actual JSON/UI controls and exact value handling.

Vero's explicit migration uses JSON data/extras objects, query auth_token and JSON tag arrays on api.getvero.com/api/v2, replacing the ambiguous original body/form helper and stringified objects. Nested null/false/empty values, lossless JSON numbers, tag spaces and empty items remain meaningful. Malformed/nonobject/duplicate/prototype-key inputs are refused. Vonage's fixed rest.nexmo.com/sms/json Basic-auth migration replaces original form credentials; no legacy fallback exists. Its seven original option descriptors include six executable options: callback, client-ref, message-class, protocol-id, status-report-req and TTL minutes-to-ms. False delivery reports, class0 and empty client-ref are preserved. Legacy account-ref, WAP Push, vCard/vCal and unused binaryPropertyName refuse before HTTP without a text fallback.

Each action needs independent confirmation of its exact input/account/callback. The selected account revision, principal, direct workspace AND current organization membership, execute permission, live setting, run/workflow and cancellation are rechecked after awaits. Transport onRequest checks again after DNS, before HTTP; there is no atomic database/socket guarantee. Organization-stored credentials are unsupported. WORKFLOW_LIVE_VERO and WORKFLOW_LIVE_VONAGE govern live execution separately.

Vonage callback requires a syntactically public HTTPS hostname URL within 100 characters and is part of the independently confirmed input. It requests a vendor outbound delivery-receipt flow; ownership, DNS, sockets, redirects and delivery remain uncontrolled/unverified. No receiver, polling or receipt proof is supplied. SMS charges, segmentation, trial restrictions and permissions remain unverified. All operations make one attempt even under maxTries3; no retries, redirects, extra probes, polling or readbacks. outcomeVerified:false never proves delivery or campaign/user effects. Any post-invocation uncertainty remains uncertain; inspect before repeating. Full bounded responses enter memory; ordinary inputs, selected outputs, history and downstream retention remain. Local PostgreSQL authority cases used synthetic HTTP and confirmation; no live provider, DNS/TLS, human, Review or Vero/Vonage browser proof exists.

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.

UpLead input and result choices

company.enrich uses uplead_company_enrich: provide domain or a nonblank company. person.enrich uses uplead_person_enrich: provide email, or nonblank firstname, lastname and domain. Field names keep the original casing. Original resource defaults are company and enrich; the app selects an explicit operation. All identifier controls start as empty text. Original descriptors did not mark these fields required, but the native validator requires one complete lookup alternative. Whitespace is preserved, not silently trimmed into a different lookup; domain/email syntax and bounded strings are validated. An empty optional value stays meaningful, while a wholly empty lookup is rejected before HTTP.

The fixed GET destinations are https://api.uplead.com/v2/company-search and /v2/person-search; identifiers are shared with UpLead and may consume credits. Selected company fields include identity/domain, address/contact data, industry/classification, revenue/employees and social URL metadata; selected person fields include identity, job/contact data, location, employer/domain and social URL metadata. Available-credit data and unknown fields are omitted after scanning the full bounded response. Output is data plus outcomeVerified:false; data may be an object, array or null. A null/no-match result does not prove nonexistence, and optional field presence is not guaranteed. Returned URL fields are never fetched.

OneSimpleAPI operation choices

The original resource defaults are website/pdf, socialProfile/instagramProfile, information/exchangeRate and utility/validateEmail; the app uses explicit definitions. Native credential auth remains query token plus output=json, separate from the input field named output.

Options is one JSON object textarea, not separate nested widgets. A selected boolean stays boolean, including false; omitted options remain omitted. PDF's original selected-option defaults are page empty/force false; screenshot's are screen empty/force false/fullpage false; SEO's headers false. These describe original option selection, not insertion of every option into an empty object. Unknown keys and malformed/type-mismatched values are rejected. Original output was shown only for download:true; the native descriptor exposes it with default data, while binary mode still refuses. It must be an identifier-shaped string and does not rename the native data result envelope.

Text inputs support expressions that retain the resolved type; defaults do not silently stringify an object or number. The download switch is a literal boolean. Operation controls use the original labels and actual native field names; the Help controls and disclosures are translated, but this is not a claim that every raw operation label is localized.

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 and PostBin native actions

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.

createList takes required name and Type (COMPANY by default, or PEOPLE). It sends name and entity. addItem defaults to PEOPLE and requires a list UUID. Original people mode requires first_name and last_name, plus optional peopleAdditionalFields: full_name, email, company_name, current_position, domain, linkedin_url, location, contact_id. Original company mode uses company_name, separate native name, and optional companyAdditionalFields: linkedin_url, domain, location, contact_id.

Alternatively supply fields JSON alone, without original top-level identity fields or either additional-fields collection. Supported keys are first_name, last_name, full_name, linkedin_url, company_name, current_position, domain, location, name, email, contact_id. PEOPLE requires two nonempty documented identity fields from linkedin_url, name, location, first_name, last_name, full_name, company_name, current_position; email/domain/contact_id alone do not satisfy this rule. COMPANY requires domain OR separate name and location. company_name never silently becomes name. Entity-incompatible fields and mixed input modes refuse before HTTP. Strings preserve case, spaces and numeric-looking values such as "0007"; empty optional strings follow original truthy-string omission. Email and LinkedIn URL syntax is validated; this does not prove identity.

listOptions replaces the automatic list loader with one explicit confirmed GET: choose Type and zero-based page (default 0, maximum 1000000). The documented page contains ten records; selected options filter entity and preserve hasNextPage, total and incompleteness. Supply the next page explicitly; there is no automatic pagination or Save/Test request. Workflow options, workflow-hook create/check/delete and LoneScale triggers remain unavailable because current route/authentication/output, callback authenticity and durable ownership contracts are unresolved. GET /webhooks is a different contract and is never substituted.

PostBin supports createBin, getBin, deleteBin, getRequest, removeFirstRequest and sendRequest. Bin creation has no required content. Get/delete require binId; get request also requires requestId; consume-first requires binId; send requires binId and defaults binContent to an empty string. Use a finite safe opaque ID (ASCII letters, digits, _ or -, at most128 characters, beginning with a letter or digit), or an exact supported original numeric bin URL/label. This explicit migration accepts documented opaque IDs as well as the original numeric form. Bin IDs api/b and request ID shift are refused where they would select another route. A read alias never consumes the first request.

removeFirstRequest uses GET /api/bin/{binId}/req/shift but removes data: treat it as an external write and confirm it independently. deleteBin uses DELETE; HTTP200 does not prove that the bin previously existed. sendRequest POSTs native JSON {"content":string} to the exact bin: this is an explicit serializer migration, not proof of the original generic serializer. Empty text is intentional. Stored false, null, zero, empty strings/arrays/objects remain distinct; selected JSON number lexemes become exact strings without rounding. Bin results expose selected ID, numeric timestamps/ISO forms and constructed request/view URLs. Request results expose selected method/path/headers/query/body/IP/timestamps; send returns a request ID. Returned links are never followed and no readback proves delivery.

Request Options is one JSON-object textarea, not separate native switches. All four original options have an explicit disposition:

The actual HOST item plan validates every item before the first HTTP request, accepts at most100 items with the same pacing policy, and executes sequentially. Aggregate interbatch waiting is at most30000 ms. It confirms and rechecks current authority for each item, pairs each result with its input and stops after failure while retaining prior receipts in failed output. It does not automatically resume or provide durable continuation. The custom timeout starts with each native invocation; outer pacing, confirmation and database latency are separate. Local limits do not prove wire/allocation or operating-system confinement.

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.

Stackby rows and paging

Choose row.append, row.delete, row.list or row.read. Supply a Stack ID and table name. Read also takes a record ID; delete takes an array of one to ten row IDs. Append accepts one to ten records, each with a field object, or Original items with each item's Stack ID, table, comma-separated columns and item JSON. Original-item migration preserves destination grouping and input indices, splits physical writes into groups of at most ten rows, and retains every batch receipt. A partial failure does not erase earlier receipts or authorize automatic replay. Read, list and append require outputFields, an array of one to fifty field names; missing vendor values remain missing, separately from false, null and empty values.

List takes an explicit Page or Complete mode. Its original returnAll:true and limit:1000 defaults express intent; they do not establish completeness. Native controls include offset (default 0, maximum 1000000), page size (default 100, range 1..100), limit (1..1000) and view (default empty text). Page mode returns an explicitly incomplete page. Complete migration persists its plan and waits between windows; every later physical page needs a fresh independent confirmation. It stops on an observed empty page or a local bound, without inventing a total or guaranteeing all provider rows. Process-local pacing cannot control other clients. API Beta compatibility remains unverified with a real account.

Dropcontact enrichment and status

Choose enrich to submit a contact or fetchRequest to read one exact requestId. Enrichment has an Email field (default empty text), Additional Fields JSON (default {}) and Options JSON (default {}). Additional fields are num_siren, siret, company, country, first_name, full_name, last_name, linkedin, phone and website. Options accept waitTime in seconds (1..86400, effective default 45), siren and language (en or fr). Original defaults are Simplify false, French company enrichment false and language English. Preserve explicit false and omitted options separately.

Enable Simplify (submit job only) for a single submission. Its request ID does not establish completed enrichment. With the original Simplify false default, the workflow persists a configurable timer (45 seconds by default), then opens a separate Human Task before one confirmed status GET. A pending result stays pending; there is no hidden polling. Completion migration needs the durable runtime and Human Tasks and refuses before sending inside loops, parallel blocks, subworkflows and single-step execution. Submit-only and explicit status reads are separate available choices.

A custom public HTTPS callback URL asks Dropcontact to deliver contact data to that exact address. Existing account callbacks may also receive it. Review this sharing before confirmation; the application neither probes the URL nor establishes receiver ownership, vendor DNS, redirects or delivery. Contact requests may consume credits. The ten-second physical-request budget excludes the outer timer, human decision and database waits.

Oura profile and daily scores

Choose profile.get, summary.getActivity, summary.getReadiness or summary.getSleep. Profile has no input fields and excludes email from its selected result. Sleep returns a daily sleep score, rather than sleep periods. Profile and summary numeric JSON values are returned as exact decimal text; omitted optional fields remain omitted and null remains null.

Every summary requires explicit startDate and endDate calendar dates in YYYY-MM-DD, with at most 31 inclusive days. This replaces the original timezone-dependent datetime and omitted-date defaults. Limit is 1..10 (default 5), applied locally and never sent to Oura. Optional nextToken selects one explicit provider page; there is no Return All or automatic pagination. receivedCount, returnedCount, omittedCount and locallyTruncated describe only that page. upstreamHasNextPage and nextToken describe upstream continuation: advancing the token cannot recover rows omitted locally from the preceding page. Raising the limit and rerunning requires another confirmation and is not a completeness guarantee.

Oura receives personal and health-data requests. The full bounded upstream response, including fields later discarded, enters memory before projection; selected outputs and ordinary history/downstream retention remain. No live token, identity, subscription, consent, scope or health-data accuracy verification is implied. Flow remains research-only because authority for its former API could not be established; it is not an available integration.

The registered catalog contains 204 providers, 2,381 operations and 2,342 tools. The 811-row reference ledger has 366 partial service rows, 430 unassessed rows and 15 service-only unimplemented-trigger rows. Stackby and Dropcontact add ordinary and Tool coverage with their selected operation aliases; Oura adds partial service coverage with zero import aliases. These counts do not establish complete n8n parity or real-provider verification.

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 and KoBo ordinary workflow requests

The native Telegram public-token and KoBo instance-token profiles add explicit ordinary-action contracts. Telegram setup covers 23 synchronous actions and KoBo setup covers 17 JSON/metadata actions. Saving the selected encrypted account does not verify it or approve an external request.

A Telegram location input preserves zero and false literally:

{
  "parameterSchemaVersion": 2,
  "wireMigrationAcknowledged": true,
  "sourceVersion": 1.2,
  "chatId": "101",
  "latitude": 0,
  "longitude": 0,
  "replyMarkup": "none",
  "additionalFields": { "disable_notification": false }
}

A KoBo form-get input explicitly acknowledges migration and raw retention:

{ "parameterSchemaVersion": 2, "migrationAcknowledged": true, "rawRetentionAcknowledged": true, "formId": "assetA" }

KoBo list-page operations additionally require singlePageAcknowledged: true and an explicit limit from 1 to 1,000. File-get metadata requires download: false; file-create URL mode sends metadata only. Telegram single-media requests require binaryData: false. Binary transfers and sendAndWait are refused, not converted into a successful JSON send.

An original-actor Human Task signs the exact request for up to 15 minutes. The runtime rechecks workspace and organization membership, request/account revisions and the consumed approval before one physical attempt and before OUTPUT. The actual materialized output must match its authenticated settled result. Unknown outcomes do not automatically resend, redirect, refresh or read back, including workflows configured with retries. Raw body and source item envelopes remain bounded and can contain personal data or downstream secrets. HTTP acceptance never proves later delivery or verified remote state. Local coverage uses simulated provider/storage; Review, provider credentials, real DB/Redis and native sockets remain unverified.

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 integration actions

Provider halopsa exposes twenty ordinary actions: clients, sites, tickets and users each support create, delete, get, update and getAll for one explicitly acknowledged page. Use the exact manual profile and schema-2 migration, with original-actor request approval and current workspace and organization execution access. Results carry protected cardinality/digests with encrypted checkpoint content; remote effects remain unverified. See operations and examples.

GoToWebinar integration actions

Provider gotowebinar exposes 23 ordinary attendee, coorganizer, panelist, registrant, session and webinar actions using schema-2 migration and an existing manual bearer profile. One original-actor approval binds the current workspace AND organization, account, request and consumed task/wait; one durable claim permits at most one request with no automatic replay after uncertainty. Lists read a single explicit page. Public output contains protected response-file references and counts, with no direct business-field chaining. Sequence recurrence remains unsupported. See the exact operation IDs and inputs.

Clearbit and Medium conditional actions

Providers clearbit (three actions) and medium (two actions) use explicit schema 2 and an existing saved policy/key/token profile. Autocomplete is keyless; enrichment and Medium require separately verified existing eligibility. One original-actor confirmation with current workspace AND organization rights authorizes at most one physical request. Outputs expose bounded business JSON, raw response and source-item ledgers in ordinary authorized history. Pending enrichment and uncertain outcomes do not authorize polling or resend. See operation IDs and controls and account prerequisites.

FileMaker integration actions

Provider filemaker exposes record, records, find, create, edit, performscript, duplicate and delete, with ordinary n8n-nodes-base.filemaker action aliases. Schema 2 requires explicit migration, manual-session, raw-retention and one-attempt acknowledgments plus a separate original-actor confirmation. Current workspace AND organization authority, selected-account revision, published node/input, original task ID AND wait token and execution lease remain bound through physical claim, success/failure settlement and freshly authenticated output.

result.data is the validated {response,messages} envelope, including actual field/portal data, record/modification IDs or script result where applicable. Bounded rawBodyUtf8 and sourceItemsJson retain the raw JSON and original single-envelope source shape; safe headers expose only content-type. These are ordinary authorized history and downstream mapping data, possibly including PII. Every messages code and returned script error must be string 0; HTTP 200 alone does not prove success or a remote effect. See inputs and limits.

Bitwarden integration actions

Provider bitwarden exposes the fourteen actions in the block reference. Tool IDs are bitwarden_ plus the operation ID with dots replaced by underscores. Original aliases require ordinary n8n-nodes-base.bitwarden numeric version 1. Every request requires explicit schema-2 repair, a supported saved account, the unchecked acknowledgments and separate original-actor confirmation.

The strict result includes validated data, bounded rawBodyUtf8, sourceItemsJson, response digest, counts, attempts:1, unknown paging completeness and outcomeVerified:false. Event continuation metadata may be used only in a separately confirmed next request. Collection/group/member current schemas have no page selector: pageMaxItems refuses an oversized response, never sends a provider limit or slices data locally. No list is called complete.

Useful business fields and raw/source JSON are ordinary authorized history and may reach downstream mapping/routing/AI. False, zero, null and empty values remain distinct when admitted by the current schema; unknown models refuse. HTTP acceptance never verifies membership/deletion effects. Current actor/workspace AND organization authority, account revision/live policy, immutable node/input/request, original task ID AND wait token and execution lease are checked before dispatch and fresh output. Failure bookkeeping compares the current consumed wait, approval and task with the captured original task/wait pair and in-flight claim. A replacement leaves the authoritative claim in flight rather than recording failure against a different approval; unchanged-lineage timeout or abort can record failure under the existing execution-lease fence. Neither state renews authority or authorizes another send.

Cortex and n8n software Public API integration actions

Provider cortex, credential cortexExistingApiKeyV1, registers only job.get → cortex_job_get and job.report → cortex_job_report, with exact ordinary n8n-nodes-base.cortex aliases. Provider n8n-public-api, credential n8nPublicApiKeyV1, registers nine actions: credential.getSchema, execution.get, execution.getAll, workflow.get, workflow.getAll, audit.generate, credential.delete, execution.delete and workflow.delete, with the ordinary n8n-nodes-base.n8n aliases and n8n_public_api_<resource>_<operation> tool IDs. Labels and fixed methods/paths, synthetic inputs and useful output mappings are in Block reference.

Underlying node output is result.data; the runtime node JSON exposes its business fields directly as node.<id>.json.data. Cortex pending reports and n8n execution status remain pending provider state, and a returned nextCursor requires a separately configured and confirmed request. Audit Generate is an explicit POST with provider-controlled effects. No full node parity, automatic paging/polling or external certification is claimed.

The original run actor must confirm the exact resolved request with current workspace AND organization execution access. Selected encrypted account revision, published node/version, run input, live-policy generation, original task ID AND wait token and execution lease remain bound through one winning durable claim, settlement and fresh authenticated output. A replaced task never renews consent. One physical attempt is allowed, including workflow maxTries3; timeout, reset, rate limit or an uncertain used claim never triggers automatic resend, readback, redirect or refresh.

Names, IDs, tags, schema option labels, job/report fields and audit locations may contain personal data retained in ordinary run, checkpoint, Human Task history and downstream mappings or AI. The key uses existing credential encryption; this adds no raw-database encryption, automatic deletion/TTL, scanner or deletion guarantee. Local bounds are 64 KiB input, 1 MiB complete response, depth 32, 20,000 nodes, 4096 reads and thirty seconds for the whole invocation, rather than vendor guarantees. Real provider authentication, selected-instance permissions/schema/version/entitlement, durable DB/Redis recovery, native DNS/TLS/sockets, Review tutorials and real AI request interpretation remain untested; local production-owner tests use simulated dependencies.

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.

Example typed read

After reviewing the retention and one-request decisions, configure this synthetic native input with your selected saved account:

{
  "parameterSchemaVersion": 2,
  "migrationAcknowledged": true,
  "rawRetentionAcknowledged": true,
  "onePhysicalAttemptAcknowledged": true,
  "tableName": "SyntheticRecords",
  "key": { "pk": { "S": "synthetic#1" } },
  "consistentRead": true,
  "projectionExpression": "#amount",
  "expressionAttributeNames": { "#amount": "amount" }
}

A returned amount such as {"N":"9007199254740993"} remains that exact string. A missing item instead returns operationData:{found:false}. Reads and writes can incur AWS charges; evaluated-item and byte limits are not a billing cap.

AWS ELB ordinary actions

Provider aws-elb exposes seven ordinary numeric-v1 aliases and tools aws_elb_listenerCertificate_add, aws_elb_listenerCertificate_getMany, aws_elb_listenerCertificate_remove, aws_elb_loadBalancer_create, aws_elb_loadBalancer_delete, aws_elb_loadBalancer_get and aws_elb_loadBalancer_getMany. All send signed GET Query2015-12-01 to a fixed regional elasticloadbalancing HTTPS443 endpoint; classify side effects by actual Action. Add/remove/create/delete are writes and always require confirmation. This is partial service coverage, with no Tool/Trigger/full-node parity claim. 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 admin actions

The public preview aws-cognito manifest registers exactly thirteen ordinary group5/user7/userPool1 actions from numeric source version1. Each uses one pinned regional cognito-idp JSON1.1 POST with AWSCognitoIdentityProviderService target and manual SigV4. Tool/Trigger and OAuth/login-provider parity are unavailable. Useful exact bounded business metadata, arrays of named attributes and target-specific opaque cursors appear in operationData; unknown and password/credential echo fields fail closed. See inputs and write 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

Provider odoo registers exactly contact.get and contact.getAll, with ordinary numericversion1 aliases only. One signed original-actor approval explicitly authorizes TWO POST /jsonrpc requests: common.login then object.execute res.partner/read or bounded search_read. The result exposes useful bounded contacts, distinct no-record, attempts:2 and outcomeVerified:false; full node/Tool/Trigger/authentication-lifecycle parity is unavailable.

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.

The three saved acknowledgment properties themselves must be literal true, independently of resolved request or trigger input. Expressions cannot grant consent, including restoration of an older signed WAIT; business fields retain their existing expression support. Invalid original or draft values remain unchanged through export/reopen until deliberate repair.

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

Generic S3 first-page action

Provider generic-s3 exposes only file.getAll.firstPage through tool generic_s3_file_getAll_firstPage, with the exact saved genericS3ManualSigV4V1 account and WORKFLOW_LIVE_GENERIC_S3 plus the workspace live preference. Input uses schema version 1, explicit bucket/prefix/limit and literal migration, first-page and data-retention acknowledgments. Current original-actor, organization/workspace, account revision, node/input, Human task/wait/decision and lease checks bind one physical claim and one native signed GET. The useful operationData carries decimal-string object sizes, retained zero-size/folder objects, partialPage:true, pageCount:1 and inert optional continuation metadata. There is no discovery, subsequent page, write, retry or generic HTTP fallback. See the bounded contract; real provider and durable persistence verification remain outstanding.

Redis ordinary string GET

Provider redis, operation string.get and tool redis_string_get implement only exact ordinary numeric-v1 GET with explicit string key type, literal output name and dotNotation:false. A separately saved redisManualTlsV1 external account and three literal boolean acknowledgments are required; imported raw consent, unsupported versions/options/operations and credential references stay in the source ledger. Tool/Trigger and full-node parity are unavailable.

One current original-actor Human decision, owned lease and physical CAS claim permit AUTH/SELECT plus one native TLS GET. Useful text is returned unchanged, missing keys return null with missing:true, empty string remains empty, and WRONGTYPE fails. The single-use owner bounds the entire invocation to thirty seconds, reply bytes to one MiB and reads to 128, with no HTTP gateway, queue credential, enumeration, retries, reconnect or resend. Fresh OUTPUT revalidates the consumed receipt and current authority. Real provider/native network, durable DB/Redis restart and Review remain untested. See the fields and limits.

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 ordinary read subset

Provider firebase-realtime-database has the original read get / tool firebase_get, using the exact separate saved firebaseRealtimeManualBearerV1 account and one nonroot literal path. No public generic HTTP wrapper, Tool/Trigger alias, root/discovery, pagination or OAuth refresh. All imports require numeric ordinary version1 and an explicit supported operation. The per-invocation host requires current original-actor workspace AND organization authority, live controls, signed Human decision, matching wait/stable decision/current owned lease and one CAS physical attempt before a native public DNS/TLS-pinned HTTPS request. Response decoding is bounded/fatal UTF8 and final OUTPUT needs its fresh signed receipt; fresh resumes cannot resend. See the exact contract and untested boundaries.

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 bill.get

Provider quickbooks exposes only ordinary numeric-v1 bill.get, tool quickbooks_bill_get. Input is parameterSchemaVersion:1, exact decimal-string billId and initially unchecked acknowledgeFinancialDataPersistence, which must be literal true. Realm/environment come from the exact saved quickbooksBillManualBearerV1 account. One fixed Intuit production/sandbox GET uses minorversion=75, the floor/default rather than a frozen schema; no generic fetch, redirect, retry, list or OAuth refresh is provided.

The exact string-ID open Bill and exact rawResponseJson enter ordinary financial/contact-data history and downstream persistence. Unsafe integers, duplicate keys, Fault or missing/mismatched Bill fail. Current organization AND workspace/original-actor/account/decision/lease/checkpoint authority and one physical claim bind persistence and fresh no-resend OUTPUT. See full fields and limitations. Real provider/native network, durable database/restart and Review remain untested.

Native PG bounded read

The distinct native-pg-read integration exposes only query.execute (native_pg_read_query_execute) with the exact saved type nativePgReadManualTlsV1. Saving a connected account records local setup and leaves authentication, privileges and server semantics unverified. It does not discover schemas or test a connection. Invocation requires the separate explicit profile, reviewed literal SELECT, one actual input item, three raw literal acknowledgments, current organization and workspace authority and exact original-actor Human approval. One physical attempt has no retry or fallback. See account setup and input/output limits. Actual provider/native/Review behavior remains untested.

En español: la integración independiente native-pg-read solo expone query.execute con la cuenta manual TLS exacta. Guardar registra la configuración local sin verificar acceso ni conectar. Ejecutar exige el perfil y SELECT literal revisados, un elemento de entrada, tres confirmaciones literales y otra aprobación Human con acceso vigente al workspace y a la organización. Solo hay un intento físico, sin reintentos ni alternativas. El comportamiento real del proveedor, nativo y de Review sigue sin probarse.

LDAP base-search migration

The preview native-ldap-read provider has one operation, search.base / native_ldap_read_search_base, and the exact separate nativeLdapReadManualLdapsV1 account. Saving this connected account is local and unverified. Execution requires one actual input, matching reviewed DN/projection/equality selection, three literal acknowledgments, current organization AND workspace authority and a separate signed original-actor Human decision. One durable physical claim owns the connection and raw close; used or uncertain claims have no automatic replay. Genuine LDAP code4 remains partial/error and inventoryComplete:false is preserved. This explicit9.2.0 SDK migration does not provide full original LDAP action/version parity. See account fields and limits. Real directory, deployment and Review behavior remain untested.

En español: el proveedor preliminar solo ofrece search.base con la cuenta LDAPS manual exacta. Guardar no conecta ni verifica acceso. Ejecutar exige selección revisada, una entrada, tres confirmaciones literales, acceso vigente a organización Y espacio y otra decisión Human firmada del actor original. No hay repetición de intentos usados o inciertos; código4 conserva su estado parcial/error.

MySQL reviewed row

native-mysql-read exposes only select (native_mysql_read_select) for an exact ordinary n8n MySQL 2.5 finite select migration and explicit nativeMySqlReadManualTlsV1 account. Save records unverified local setup. Execution requires one actual input, literal matching reviewed table/columns, three literal acknowledgments, current original-actor organization AND workspace authority and separate exact Human approval. One durable physical claim permits one TLS session/query; no retry, pool, reconnect, discovery or fallback. Fresh OUTPUT checks signed original task/wait/decision/lease and retained business data. The account contract and limits apply. Owned local protocol tests do not certify user grants, public DNS, deployment, durable restart or Review.

En español: la integración independiente solo permite una selección literal revisada de MySQL 2.5, una cuenta TLS manual, un elemento y otra aprobación Human del actor original con acceso vigente a la organización y al workspace. Hay un intento físico, sin reintentos ni alternativas; guardar no verifica permisos. Las pruebas locales no certifican el servidor del usuario ni Review.

MongoDB bounded document/find

The preview native-mongo-read provider exposes only document.find / native_mongo_read_document_find with a separate manual account. Actual original input, saved source, current actor/organization AND workspace/account authority, signed Human decision, same-CAS physical claim and fresh OUTPUT admission are mandatory. Used or uncertain claims never replay. This explicit SDK 7.7.0 migration is a finite subset, not full n8n parity. See the manual account, the block and EJSON output, and the admitted original import syntax. Real provider credentials, deployment packaging and authenticated Review remain unverified.

En español: El proveedor preliminar solo admite document.find con cuenta independiente, una entrada, fuente literal, autoridad vigente y decisión Human firmada. El claim duradero se guarda en el mismo CAS; los intentos usados o inciertos no se repiten.

Jina Reader finite migration

jina-reader/reader.read binds native_jina_reader_reader_read to a fixed-origin HTTPS Reader owner and manual jinaReaderManualKeyV1 saved account. WORKFLOW_LIVE_NATIVE_JINA_READER=true and the workspace live preference must both be current. The separate original-actor Human task signs the exact URL/input/account/source revisions. A checkpoint lease/revision CAS consumes one physical claim; authenticated receipt, task/wait/decision lineage, current organization AND workspace authority and result/raw digests are revalidated at OUTPUT. A used, failed or uncertain claim never authorizes retry. See fields and retained output.

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)

The separate provider aws-rekognition exposes only rekognition.image.detectLabels, through tool aws_rekognition_image_detectLabels. It accepts one explicitly versioned S3 image in us-east-1. Generic image/analyze aliases, other detectors, binary upload, custom endpoints, credential discovery and automatic retries are unsupported. Saving a credential or importing a source grants no execution authority.

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

El proveedor separado aws-rekognition expone únicamente rekognition.image.detectLabels, mediante la herramienta aws_rekognition_image_detectLabels. Acepta una imagen S3 con versión explícita en us-east-1. No admite alias genéricos image/analyze, otros detectores, carga binaria, destinos personalizados, descubrimiento de credenciales ni reintentos automáticos. Guardar una cuenta o importar un origen no concede autoridad de ejecución.

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 finite provider is aws-textract, action textract.analyzeExpense, tool aws_textract_analyzeExpense. It makes one AnalyzeExpense request to the fixed regional service with a manually selected native account. It does not expose an arbitrary AWS URL, S3 document reference, discovery, generic Textract action or automatic retry.

Output contains httpStatus:200, optional requestId, complete parsed raw, exact rawJson, its SHA-256 and a JSON-pointer numericLexemes ledger. Missing and empty ExpenseDocuments remain distinct. Unrecognized business fields are preserved. Unsafe integers, nonfinite numbers, nonzero underflow, malformed or oversized responses and reflected credentials refuse successful output. The raw response is limited to 1 MiB; retained output is limited to 4 MiB. Local simulated responses do not verify OCR accuracy or provider compatibility.

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 proveedor finito es aws-textract, acción textract.analyzeExpense, herramienta aws_textract_analyzeExpense. Hace una sola solicitud AnalyzeExpense al servicio regional fijo con una cuenta nativa elegida manualmente. No permite URL AWS arbitraria, referencias de documentos S3, descubrimiento, acciones genéricas ni reintento automático.

La salida contiene httpStatus:200, requestId opcional, raw completo, rawJson exacto, su SHA-256 y un registro numericLexemes por puntero JSON. Se distingue entre ExpenseDocuments ausente y vacío. Se conservan los campos de negocio desconocidos. Enteros inseguros, números no finitos, subdesbordamiento distinto de cero, respuestas malformadas o demasiado grandes y credenciales reflejadas impiden una salida exitosa. La respuesta sin procesar tiene límite de 1 MiB y la salida retenida de 4 MiB. Las respuestas locales simuladas no verifican OCR ni compatibilidad real.

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.

Google directory raw get operations

Google Chat adds spaces.getRaw (googlechat_spaces_getRaw); Google Contacts adds contacts.getRaw (googlecontacts_contacts_getRaw). Both use the existing canonical integration executor, current selected manual account, live control and independent confirmation. Literal full-record retention acknowledgment and exactly one actual input are required. They return the complete bounded correlated record; Contacts additionally adds contactId. Existing metadata operations keep their schemas. Ordinary numeric n8n v1 imports support only explicit OAuth Chat space/get and explicit raw Contacts contact/get with the five-field subset. See the exact inputs, bounds, privacy and refusals. Provider and authenticated Review execution remain unverified.