Connect GoFlow 3PL Logistics to Pipe17

Use this connector to:

• Push shipping requests from Pipe17 into GoFlow for fulfillment
• Pull fulfillment confirmations from GoFlow back into Pipe17
• Sync warehouse inventory levels from GoFlow into Pipe17
• Detect orders canceled in GoFlow and update Pipe17 shipping request statuses accordingly

Supported API version: GoFlow REST API v1
Authentication: API Key
Rate limits: 60 requests/min (GET), 30 requests/min (POST/PUT), 6 requests/hour (async reports)

Setup

Prerequisites

Before configuring the connector, ensure you have:

1. An active GoFlow account with API access enabled.
2. A GoFlow API Key (see step 1 below).
3. Your GoFlow subdomain URL (e.g., https://yourcompany.goflow.com).

Steps

1. Locate your GoFlow API Key

• Log in to GoFlow.
• Navigate to Settings → API Tokens.
• Generate a new token or copy an existing one.
• Store the key securely: it will not be shown again after initial creation.

2. Create a new connection

• In Pipe17, navigate to Integrations → Add Integration.
• Select GoFlow 3PL from the catalog.
• Enter API URL (e.g., https://yourcompany.goflow.com) and API Key.
• Click Connect.

Settings

Integration settings

Flows

Shipments out: Shipping Requests → GoFlow

Pushes Pipe17 shipping requests into GoFlow for fulfillment.

Trigger: Pipe17 poll for shipping requests in readyForFulfillment, canceled, or canceledRestock status.

• Use the Shipment Order IDs setting to restrict which orders are pushed during testing
• Products not recognized in GoFlow will cause the order to be rejected; ensure the product catalog is up to date in GoFlow before pushing orders

Fulfillments in: Fulfillment Confirmations ← GoFlow

Pulls fulfilled GoFlow orders and creates fulfillment records in Pipe17.

Trigger: Vendor poll (VendorPoll) against GoFlow's fulfilled orders

• Partial shipments generate multiple fulfillment records per shipping request
• Only orders that have completed the full pick-pack-ship workflow in GoFlow are returned

Inventory in: Inventory ← GoFlow

Pulls current inventory quantities from GoFlow into Pipe17 using an asynchronous report.

How it works:

1. The connector requests an inventory count report from GoFlow
2. It polls until the report is ready
3. The completed report is downloaded and processed in batches

Scheduling: The sync interval adapts based on how long the previous cycle took — intervals are bucketed at 1 hour, 4 hours, 8 hours, and 12 hours.

• Use the Inventory SKUs setting to limit the sync to specific products
• Use Force Inventory Resync to trigger an immediate full resync outside the normal schedule

Manual action: Pull inventory by SKU

The connector supports an on-demand action (inventory.in.by.sku) to pull inventory for specific SKUs immediately, without waiting for the next scheduled sync. Use this when you need an up-to-date count for a particular product.

Locations in: Warehouse Locations ← GoFlow

Pulls warehouse location data from GoFlow into Pipe17.

Trigger: Vendor poll against GoFlow's warehouse locations

Shipment cancellations in: Cancellations ← GoFlow

Detects orders that have been canceled in GoFlow and updates the corresponding Pipe17 shipping request status.

Trigger: Vendor poll for canceled GoFlow orders

• When a cancellation is detected, the Pipe17 shipping request is updated to the status configured in the Cancellation Action setting
• Default status applied is canceledRestock
• Available statuses: reviewRequired, canceled, canceledRestock, failed

Troubleshooting

Connection test fails

Shipping requests not appearing in GoFlow

• Confirm the shipping request status is readyForFulfillment — requests in other statuses will not be picked up
• Check whether the Shipment Order IDs filter is active and inadvertently excluding orders
• Review error logs for validation failures — the response will indicate which field GoFlow rejected
• Verify all product codes in the request exist in GoFlow's product catalog

Fulfillments not syncing back to Pipe17

• Confirm GoFlow has completed the full pick-pack-ship workflow for those orders
• Check that the external order reference on the GoFlow order matches the Pipe17 shipping request reference exactly

Inventory counts are stale or incorrect

• Inventory uses an adaptive sync schedule; if the previous cycle was long, the next sync may be several hours away — use Force Inventory Resync to trigger an immediate update
• If you only need counts for specific products, use the on-demand Pull inventory by SKU action instead of waiting for a full sync
• Check whether the Inventory SKUs filter is active and excluding products you expect to see

Cancellations not reflecting in Pipe17

• Confirm the Cancellation Action setting is configured to the intended target status
• Verify the order was fully canceled in GoFlow, not just placed on hold or partially canceled

Request limit errors

Rate limit retries are handled automatically — the connector will retry up to 3 times, waiting the duration specified in GoFlow's error response before retrying. If you are consistently hitting limits, reduce the frequency of manual actions or contact GoFlow support to discuss your account's limit tier.

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the app page.
• Submit a support request with as much relevant detail as possible. Learn how to submit a request.
• For urgent issues, email us directly at support@pipe17.com.

We're here to help you succeed with your operations.