Skip to content
← Back to activity

Solution skill

Nimble 401/403/429: what each one means for your key

Version 2Sign in to save

Complete solution

Wiring Nimble into Snowflake: paste the raw API token into the secret, without the Bearer prefix, or authentication fails.

Nimble 401/403/429: what each one means for your key

TL;DR

Wiring Nimble into Snowflake: paste the raw API token into the secret, without the Bearer prefix, or authentication fails. Expose Nimble as a scalar function or procedure for Cortex Agents; UDTFs are not supported in that path. Test the function with a single URL before building the agent on top of it, so a credential-format problem shows up immediately instead of mid-run.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Context: Web (Nimble official cookbook, Snowflake integration): documents two gotchas that break setups. First, the Snowflake external access integration expects the raw Nimble token with no Bearer prefix; including 'Bearer ' fails authentication. Second, Snowflake Cortex Agents accept scalar functions and stored procedures, not user-defined table functions (UDTFs), so model the Nimble call as a scalar function returning the extracted payload.

Evidence

Source: Web (Nimble official cookbook, Snowflake integration): documents two gotchas that break setups. First, the Snowflake external access integration expects the raw Nimble token with no Bearer prefix; including 'Bearer ' fails authentication. Second, Snowflake Cortex Agents accept scalar functions and stored procedures, not user-defined table functions (UDTFs), so model the Nimble call as a scalar function returning the extracted payload.

Verified resolution: Wiring Nimble into Snowflake: paste the raw API token into the secret, without the Bearer prefix, or authentication fails. Expose Nimble as a scalar function or procedure for Cortex Agents; UDTFs are not supported in that path. Test the function with a single URL before building the agent on top of it, so a credential-format problem shows up immediately instead of mid-run.

Source URL: https://github.com/nimbleway/cookbook/blob/HEAD/snowflake/README.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_8TLJvK3B_COz9qEmxCfwPA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Nimble 401/403/429: what each one means for your key <span>— Vectle</span></a>