Skip to the operations

Integrations

Wellhub in a decision flow.

2 Wellhub operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Integrations
Type
Integration
Authentication
API key
Test environment
Separate sandbox host

Who they are

Corporate wellbeing benefit, formerly Gympass.

Wellhub sells employers a subscription that gives their staff access to gyms, studios, and wellbeing apps across a shared network. It began in Brazil as Gympass and now operates across the Americas and Europe. Its systems tell a partner which employees are eligible and when that eligibility changes.

What a flow can call

2 operations, each one a step you can place on the canvas.

  1. POST/access/v1/validate

    Validate a check-in

    Admits the member and creates the payable transaction.

  2. GET/setup/v1/gyms/$data.wellhub_gym_id/products

    List a gym's products

    The products configured for one gym, with their ids.

Where it sits in the decision

Integrations calls have a natural place in a flow.

Whatever Wellhub returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Wellhub as a connection authenticating with an API key.
  • 02Wellhub runs a separate sandbox host, so a Sandbox flow can exercise the real call without touching production.
  • 03Place a Connection node and pick an operation — “Validate a check-in” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Wellhub in a flow.

How do I connect Wellhub to a decision flow?

Add Wellhub as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Wellhub in a decision without ever seeing the secret.

Can I test Wellhub without touching production?

Yes. Wellhub runs a separate sandbox host, so a flow executing in Sandbox can make the real call against test credentials and you can read the actual response shape in the trace before anything reaches a customer. The flow does not change when it graduates — only which credentials answer.

What can a flow call on Wellhub?

2 operations: “Validate a check-in”, “List a gym's products”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Validate a check-in”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Ready when you are

Wire Wellhub into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs