Get run step statuses
Read selected visible native step IDs/statuses; no mutation, files, polling or inferred whole-run health.
Connector library
First Resonance ION connector.
Read selected ION run-step IDs and native statuses through a named bounded commercial GraphQL query with a managed issued access token.
Connector download
Download First Resonance ION
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.0 Choose version
- Release
- 2026-10-04
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- Environment
- Package size
- 7 KB
- SHA-256
1b4bb25f7fc33e060cb2e865523bb351a6faefb194c6767d1a16ceba509e7809
Version history
What's new
- v0.2.0.0Latest · 2026-10-04 · Implemented source
Replaces the generic scaffold with a fixed commercial GraphQL run-step status read, managed issued access token, exact native selected fields and bounded failure handling. No writes or whole-run health inference.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical readable HTTP scaffold; immutable archive retained.
Included in this version
Included actions
Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.
Vendor API
API and access
Implementation considerations
- Store only the approved issued access token in a managed token credential. The specific access-token guide and linked helper send raw Authorization without a Bearer prefix. A general file-upload example differs; confirm live acceptance without automatic format fallback.
- Explicit commercial sandbox/production targets use staging-api.buildwithion.com/graphql or api.buildwithion.com/graphql. Arbitrary hosts, Gov Cloud and Australian regional endpoints are excluded. Run ID uses a positive int32 subset; it is requested context rather than echoed identity.
- Native step IDs retain numeric values in a declared local 14-digit subset; exact status labels use a local ASCII token subset, without guessed enums or success/failure normalization. Maximum 1000 steps; no pagination, polling or complete-visibility claim.
- GraphQL errors, including partial results, null/missing run data and HTTP 404 remain failures. Empty step lists are scoped reads without inferring global absence or run completion. Files, etags, signed URLs and writes are omitted.
- Strict JSON/media/UTF-8, a 1 MiB response cap, normal TLS trust and a shared 1–8 second budget fail without redirects, proxies or replay. Hosted import, dependencies and live environment/token/header/permission/ID/status behavior remain untested.
- One packaged commercial GraphQL run-step status read follows the specific access-token guide and official helper's raw Authorization form. Hosted dependencies and live token/header/permission behavior need validation.
Related connectors
More in Enterprise, ERP & HR APIs
Support
Need help with First Resonance ION?
Tell us what you need to connect or change.