GoHubX
GoFlow

Integrations, workflows and mappings

GoFlow is the integration toolset GoHubX customers run in production today. Build workflows visually, map documents without hand-coding, and run them on a schedule or as messages arrive.

  • Built for
  • Integration developers on GoHubX projects
  • Integration operations teams
  • GoTatva implementation consultants
The challenge

What gets in the way today.

Integrations buried in code

Hand-written scripts are hard to read, test and hand over.

Messages lost during maintenance

Stopping an integration can mean partners' messages are refused.

Hard to find a transaction later

Tracing one order through many runs takes far too long.

What you get

What changes with GoFlow.

01

Visual workflows

Lay out what should happen, add decisions and error handling, and test with sample input.

02

Mapping without hand-coding

Turn one document shape into another by connecting fields, with rules where codes differ.

03

Scheduled or event-driven

Run integrations on a schedule or whenever a message arrives.

04

Pause without losing messages

Hold incoming messages while you make changes, then resume.

05

Find any transaction

Look up a transaction by order number or reference and report on it.

VisualWorkflows you can read
MappingNo hand-coding required
Safe pauseMessages held, not lost
TraceableFind transactions by reference
Built on GoHubX

One platform under every product.

GoFlow runs on GoHubX, so it shares the same security, audit trail and support as everything else you run with us.

Every change on the record

Who did what, and when, in a tamper-evident audit trail.

Credentials in a vault

Never shown again after saving.

Self-service, managed or hybrid

Run it yourself, let our team run it, or mix the two.

FAQ

Questions about GoFlow.

Is GoFlow being replaced?

GoFlow Next is the new generation. GoFlow keeps running unchanged, and integrations can be brought across to GoFlow Next when you are ready.

Can GoFlow handle EDI?

Yes. GoFlow reads, writes and checks EDI as part of a workflow.

Where are passwords kept?

In a vault, never shown again after saving, and masked in logs.

Can I hold incoming messages without refusing them?

Yes. Pausing holds what arrives until you resume.

Let's talk

See your own documents flow through GoHubX.

Bring one partner, one carrier or one process. We will show it running on GoHubX.

Or write to us directly
sales@gotatva.com
deepak.joshi@gotatva.com