inFlow Inventory Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to an inFlow Inventory location.

inFlow Inventory

1. Click the + icon on the Nexset that will be sent to the inFlow Inventory destination, and select the Send to Destination option from the menu.

2. Select the inFlow Inventory connector from the list of available destination connectors. Then, select the credential that will be used to connect to the inFlow Inventory organization, and click Next; or, create a new inFlow Inventory credential for use in this flow.

3. In Nexla, inFlow Inventory destinations can be created using pre-built endpoint templates, which expedite destination setup for common inFlow Inventory write operations. Each template is designed specifically for the corresponding inFlow Inventory endpoint, making destination setup easy and efficient.
   • To configure this destination using a template, follow the instructions in Configure Using a Template.

   inFlow Inventory destinations can also be configured manually, allowing you to send data to inFlow Inventory endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common inFlow Inventory endpoints. Each template is designed specifically for the corresponding inFlow Inventory endpoint, making destination setup easy and efficient.

Endpoint Settings

• Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your destination for this endpoint.

  Create Product

  Creates a new product record in inFlow Inventory. Use this endpoint to onboard new products from e-commerce platforms, supplier feeds, or product information management systems.

  • Sends a POST request to /products (prefixed with your Company ID) with a JSON payload describing the new product.
  • No path parameters are required for product creation; all product fields (name, SKU, pricing, etc.) are provided in the request body.

  The inFlow API enforces a rate limit of 60 requests per minute. For large product catalogs, enable record batching to reduce API calls and avoid hitting this limit.

  Create Sales Order

  Creates a sales order in inFlow Inventory from an external source such as an e-commerce platform or CRM. Use this endpoint to centralize order management in inFlow from external sales channels.

  • Sends a POST request to /sales-orders (prefixed with your Company ID) with a JSON payload containing order details including customer, line items, and payment information.
  • No path parameters are required for order creation; all order fields are provided in the request body.

  Customer IDs and product IDs referenced in the order must exist in inFlow before the order is created. Use lookup-based Nexla flows to validate these IDs before writing.

  Update Product

  Updates an existing product record in inFlow Inventory. Use this endpoint to sync product name, cost, pricing, or reorder point changes from external systems.

  • Sends a PUT or PATCH request to /products/{id} (prefixed with your Company ID) with a JSON payload containing the fields to update.
  • Configure the following parameters: Id — the inFlow Inventory product ID to update. This value must be included in the API URL path.

  Use PATCH for partial updates (only the fields provided in the body will be modified) and PUT for full record replacement. Ensure the correct product ID is mapped from your Nexset before activating this destination.

  Create Customer

  Creates a customer record in inFlow Inventory. Use this endpoint to sync customer data from CRM or e-commerce systems into inFlow for order processing.

  • Sends a POST request to /customers (prefixed with your Company ID) with a JSON payload describing the new customer.
  • No path parameters are required for customer creation; all customer fields (name, contact, payment terms, etc.) are provided in the request body.

  Newly created customers are immediately available for use in sales orders. Ensure that customer names and contacts are correctly mapped from your source Nexset to avoid duplicate records.

  Create Purchase Order

  Creates a purchase order in inFlow Inventory to restock inventory from a vendor. Use this endpoint to automate reorder point-triggered purchasing from procurement or planning systems.

  • Sends a POST request to /purchase-orders (prefixed with your Company ID) with a JSON payload containing vendor, line items, and expected delivery details.
  • No path parameters are required for purchase order creation; all order fields are provided in the request body.

  Vendor IDs referenced in the purchase order must exist in inFlow before the order is created. Use the List Vendors source endpoint to retrieve and validate vendor IDs in advance.

  Create Stock Adjustment

  Creates a stock adjustment in inFlow Inventory to correct inventory quantities. Use this endpoint to synchronize physical count results or apply inventory corrections from external audit systems.

  • Sends a POST request to /stock-adjustments (prefixed with your Company ID) with a JSON payload specifying the product, location, quantity change, and adjustment reason.
  • No path parameters are required for adjustment creation; all adjustment fields are provided in the request body.

  Adjustment reasons must match a valid reason ID from inFlow. Use the List Adjustment Reasons source endpoint to retrieve valid IDs before mapping them into this destination.

  Create Stock Transfer

  Creates a stock transfer in inFlow Inventory to move inventory between locations. Use this endpoint to automate inter-warehouse transfers triggered by replenishment rules or distribution planning systems.

  • Sends a POST request to /stock-transfers (prefixed with your Company ID) with a JSON payload specifying the source location, destination location, product, and quantity.
  • No path parameters are required for transfer creation; all transfer fields are provided in the request body.

  Both the source and destination location IDs must be valid inFlow locations. Use the List Locations source endpoint to retrieve and validate location IDs before building transfer flows.

  Update Customer

  Updates an existing customer record in inFlow Inventory. Use this endpoint to keep inFlow customer profiles synchronized with CRM or external contact management systems.

  • Sends a PUT or PATCH request to /customers/{id} (prefixed with your Company ID) with a JSON payload containing the fields to update.
  • Configure the following parameters: Id — the inFlow Inventory customer ID to update. This value must be included in the API URL path.

  Ensure the correct customer ID is mapped from your Nexset. Customer IDs can be retrieved using the List Customers source endpoint.

  Update Purchase Order

  Updates a purchase order in inFlow Inventory, such as receiving stock, changing status, or editing line items. Use this endpoint to sync purchase order updates from receiving or procurement systems.

  • Sends a PUT or PATCH request to /purchase-orders/{id} (prefixed with your Company ID) with a JSON payload containing the fields to update.
  • Configure the following parameters: Id — the inFlow Inventory purchase order ID to update. This value must be included in the API URL path.

  Purchase order IDs can be retrieved using the List Purchase Orders source endpoint. Verify order status before attempting updates, as completed or cancelled orders may not accept modifications.

  Update Sales Order

  Updates a sales order in inFlow Inventory, such as marking it as shipped, updating quantities, or changing status. Use this endpoint to sync order fulfillment updates from shipping or WMS systems back into inFlow.

  • Sends a PUT or PATCH request to /sales-orders/{id} (prefixed with your Company ID) with a JSON payload containing the fields to update.
  • Configure the following parameters: Id — the inFlow Inventory sales order ID to update. This value must be included in the API URL path.

  Sales order IDs can be retrieved using the List Sales Orders source endpoint. Verify order status before attempting updates, as fully shipped or closed orders may not accept modifications.

Endpoint Testing

Once the selected endpoint template has been configured, Nexla can send a test payload to the inFlow Inventory API to ensure that the destination is configured correctly.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually

inFlow Inventory destinations can also be manually configured to send data to any valid inFlow Inventory API endpoint. You can also configure Nexla to automatically send the response received from the inFlow Inventory API after each call to a new Nexla webhook data source.

First, select the API method that will be used for calls to the inFlow Inventory API from the Method pulldown menu. Common methods used when writing data to inFlow Inventory include:

• POST: For creating new records (e.g., new products, customers, sales orders, purchase orders)
• PUT: For fully replacing an existing record
• PATCH: For partially updating an existing record (e.g., updating a product's stock level or order status)
• DELETE: For removing records

Data Format

4. Select the format in which the Nexset data will be sent to the inFlow Inventory API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The inFlow Inventory API accepts data in JSON format.

API Endpoint URL

5. Enter the URL of the inFlow Inventory API endpoint to which you want to send the Nexset data in the URL field. The inFlow Inventory API base URL is https://cloudapi.inflowinventory.com, and all endpoints include your Company ID as a path prefix. For example:

   • Create a product: https://cloudapi.inflowinventory.com/{'{companyId}'}/products
   • Update a sales order: https://cloudapi.inflowinventory.com/{'{companyId}'}/sales-orders/{'{orderId}'}
   • Create a customer: https://cloudapi.inflowinventory.com/{'{companyId}'}/customers
   • Create a purchase order: https://cloudapi.inflowinventory.com/{'{companyId}'}/purchase-orders
   • Adjust stock: https://cloudapi.inflowinventory.com/{'{companyId}'}/stock-adjustments

   Replace {'{companyId}'} with your inFlow Inventory Company ID, which can be found on the Integrations page of your inFlow Inventory account. For update or upsert operations, include the record ID at the end of the URL.

The inFlow Inventory API enforces a rate limit of 60 requests per minute. For large data loads, consider enabling record batching to reduce the number of API calls and avoid hitting this limit.

Request Headers

Optional

• If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

  You do not need to include the Authorization header or any authentication headers already present in the credentials. Nexla automatically adds the Bearer token from your inFlow Inventory credential to every API request.

Exclude Attributes from the Call

Optional

• If any record attributes in the Nexset should be omitted when sending data to this inFlow Inventory destination, select the attributes from the Exclude Attributes pulldown menu.

• Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching

Optional

1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook

Optional

Nexla can automatically send the response received from the inFlow Inventory API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

• To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload

Sample request payloads containing a portion of the Nexset data that will be sent to the inFlow Inventory API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

• Click on a sample request payload to expand it and view the complete payload content.
• Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing

After all endpoint settings have been configured, Nexla can send a test payload to the inFlow Inventory API to ensure that the destination is configured correctly.

1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

3. Click the Send Test Data button at the top of a sample payload to send the test payload to the inFlow Inventory API using the current settings.

Save & Activate the Destination

• Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to inFlow Inventory, open the destination resource menu, and select Activate.

  The Nexset data will not be sent to inFlow Inventory until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.