Custom APIs and tokens

Not every useful integration needs a bespoke provider in Neudash.

If a service exposes a normal REST API, Neudash can usually work with it by combining:

  • a secure configuration for the credential
  • normal HTTP requests from process code
  • agent research against the provider’s API documentation

What this path is for

Use this pattern when:

  • the service uses an API key, bearer token, or other standard secret
  • the service has a REST API but no first-class Neudash page yet
  • you want to move quickly on a long-tail integration

What Neudash handles

Neudash supports secure configuration storage for:

  • API keys
  • bearer tokens
  • passwords or service secrets
  • custom credentials used by process code

That means the process code can focus on the API interaction itself rather than hardcoding secrets.

Security posture

Secrets stored in Neudash configurations are handled as secrets, not as plain config text. The goal is to let processes use external APIs without pushing credentials into code or asking operators to manually manage them inside scripts.

What the agent can do here

For a normal REST API, the agent can often:

  1. read the provider documentation
  2. determine the auth pattern
  3. create the right Neudash configuration
  4. write the HTTP logic in process code
  5. test the integration against the real API

This is the main escape hatch that keeps Neudash from being limited to a fixed connector marketplace.

When to prefer a dedicated provider instead

Use a dedicated provider or trigger when the value is not just auth. Dedicated providers are most useful when Neudash needs to own:

  • OAuth flow details
  • webhook verification
  • remote subscription lifecycle
  • row-level or event-level semantics
  • provider-specific renewal and recovery behavior

If all you need is authenticated REST access, the generic path is usually enough.

Common patterns

  • Poll a REST API on a schedule
  • Push records into a SaaS API from a process
  • Call an internal business API with a bearer token
  • Connect a niche vendor that Neudash does not yet model directly

Related docs