Skip to content
Proud to collaborate with Microsoft for Startups

neon.auth.validate_token ​

Validate a Neon API key

Validate a Neon API key by calling the current-user endpoint (GET /users/me).

Inputs: none (token comes from the neon plugin).

Outputs (terminal state_data):

  • neon_user_id: str — Neon's own user id (provider reference)
  • neon_login: str — Neon login handle
  • neon_email: str — account email

Plugin required: context.get_plugin("neon") must expose .api_token.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-neon
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidYes—Cloud connection holding the Neon credential

Output Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidNo——
neon_user_idstringNo——
neon_loginstringNo——
neon_emailstringNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "neon.auth.validate_token",
  "initial_data": {
    "connection_uuid": "value"
  }
}