STEP 1
Connect Forager and JOOR
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Forager and JOOR Integration
Connect Forager and JOOR to automate sales workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Forager and JOOR
Detailed info you need to know about Forager and JOOR integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Forager to JOOR
Set up your Forager and JOOR integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Forager and JOOR nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Forager and JOOR. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Forager and JOOR work in WEXTL?
WEXTL exposes actions and triggers for Forager and JOOR that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
JOOR triggersForager actions
JOOR modules
- Watch OrdersTriggers when an order is created or updated.
- Create CollectionsCreates one or more collections (linesheets) of products in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
- Create Collections by Product External IDCreates one or more collections (linesheets), referencing products by your own system ID instead of the JOOR product ID. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
- Create Line ItemsAdds one or more SKU line items to existing orders in a single batch call. If a SKU is already on the order, the requested quantity is added to the existing quantity. Only orders in In Progress, Notes, or Pending status accept new line items.
- Create or Update Connections in BulkCreates or updates brand-to-retailer connections in bulk.
- Create OrdersCreates one or more order objects in a single batch call. Add line items to a created order with the Create Line Items module.
- Create PricesCreates prices for your SKUs.
- Create Prices by External IDCreates prices for your SKUs using your system ID.
- Create Product AssetsUpload image, swatch, or video assets to products by source URL — JOOR downloads the file itself, no upload required. Runs as an async batch; pass the returned batch_id to Get Job Batch Status to check progress.
- Create Product Color AssetsUploads color/swatch assets to a product's SKU trait (e.g. a specific color) by source URL — JOOR downloads the file itself, no upload required. Runs as an async batch; pass the returned batch_id to Get Job Batch Status to check progress.
- Create ProductsCreates one or more products in your JOOR catalog in a single batch request, including categories, trait values, custom tags, and badge.
- Create SeasonsCreates one or more seasons in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
- Create ShipmentsCreate one or more shipment records (does not replace existing shipments for the order). The Shipping API is a paid add-on — confirm it is enabled on your JOOR account before running this module.
- Create SKUsCreates SKUs for your products.
- Delete Line ItemsDeletes one or more SKU line items from existing orders in a single batch call — all units of the line item are removed. This cannot be undone.
- Delete Price TypesDeletes your price types. A price type tied to any order that is not yet Approved or Canceled cannot be deleted.
- Delete Product AssetsRemoves one or more assets from products in a single batch call.
- Delete Product Color AssetsRemoves one or more color/swatch assets from a SKU trait in a single batch call.
- Delete ProductsPermanently deletes one or more products from your JOOR catalog in a single batch request. This cannot be undone.
- Delete ShipmentsDelete one or more shipment records by ID or External ID. The Shipping API is a paid add-on — confirm it is enabled on your JOOR account before running this module.
- Get AssortmentReturns one assortment with extended detail: brand, season, creator and editable users, currency conversions, attribute options, price modifiers, and merchandising hierarchy nodes.
- Get Assortment SKUsReturns a cursor-paginated list of SKU rows for a single assortment, including style/color/size, quantities by door, images, swatches, financials (linesheet vs actual currency), and SKU-scoped attribute options.
- Get AssortmentsReturns a cursor-paginated list of assortments for the authenticated retailer account, with optional filters (status, brands, created/modified ranges, archived state).
- Get CasepacksFetch a list of casepacks — pre-defined size/quantity groupings used when creating or updating SKUs.
- Get CategoriesFetch a list of product categories. Category IDs feed the category_ids rows on product create/update modules.
- Get CollectionsFetches a list of collections (linesheets), optionally filtered by ID, name, or archived status.
- Get ConnectionsRetrieves brand-to-retailer connections.
- Get DoorsFetch a list of retailer doors/locations. Door IDs feed the door_id field on order line item rows.
- Get Job Batch StatusChecks the progress of an asset upload batch started by Create Product Assets or Create Product Color Assets.
- Get Line ItemsFetches a list of order line items (SKUs on an order), including quantities, discounts, and warehouse delivery dates.
- Get OrdersFetches a list of orders. Supports JOOR's real page-based pagination (page/page_size/sort_by/sort_order) plus filters by status, export status, approval date, and last-modified date.
- Get PaymentsFetch payment information for orders. An order with no payments is not included in the response.
- Get Price TypesFetches a list of price types. The price type assigns a currency, wholesale price, and retail price to a SKU — use its ID in Create/Update Prices.
- Get PricesFetches a list of prices for your SKUs.
- Get ProductsFetches a list of products from your JOOR catalog, optionally filtered by IDs, season, collection, badge, custom tags, price type, currency, division, fabrication, silhouette, country of origin, material, size, or color.
- Get SeasonsFetches a list of seasons defined in your JOOR account, for mapping to collections/linesheets.
- Get ShipmentsList shipments, with optional filters by external ID, line item, status, carrier, and shipping or delivery date ranges. Includes vendor-side pagination.
- Get SKUsFetches a list of SKU data for your products. At least one of Product IDs or SKU IDs must be provided.
- Get TraitsFetch a list of product and SKU traits. Trait IDs are base64-encoded strings — pass the id through verbatim wherever a trait is referenced (e.g. product_trait_values rows).
- Make an API CallPerforms an arbitrary authorized API request to the JOOR API.
- Update CollectionsUpdates one or more existing collections (linesheets) in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
- Update Collections by Product External IDUpdates one or more existing collections (linesheets), referencing products by your own system ID instead of the JOOR product ID. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
- Update Line ItemsUpdates one or more existing SKU line items in a single batch call — for example, to change quantities, cancel a line item, or apply a discount. Only line items on orders in In Progress, Notes, or Pending status can be updated.
- Update OrdersUpdates one or more existing orders in a single batch call — for example, to change an order's status.
- Update PricesUpdates prices for your SKUs.
- Update ProductsUpdates one or more existing products in your JOOR catalog in a single batch request, identified by JOOR product ID or External ID.
- Update Products by External IDUpdates one or more existing products in your JOOR catalog in a single batch request, identified by your own system's External ID.
- Update SeasonsUpdates one or more existing seasons in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
- Update ShipmentsPartially update shipments. Only provided fields are updated. The Shipping API is a paid add-on — confirm it is enabled on your JOOR account before running this module.
- Update SKUsUpdates SKUs for your products.
Forager modules
- Get Work EmailPerforms a reverse lookup to find work emails associated with a person.
- Lookup a Person by PhonePerforms a reverse lookup of person details by phone.
- Lookup Personal EmailsPerforms a reverse lookup of personal emails for a person.
- Lookup Phone NumbersPerforms a reverse lookup of phone numbers to identify associated person details.
- Make an API CallPerforms an arbitrary authorized API call.
- Search a Person by EmailPerforms a reverse lookup of person details using an email address.
- Search Job Post EventsSearches for job post events.
- Search OrganizationsSearches for organizations.
- Search Website DetailsPerforms a reverse lookup of a website.
Frequently asked questions
Common questions about connecting Forager and JOOR.
Connect your Forager and JOOR accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when JOOR's "Watch Orders" fires, WEXTL can "Get Work Email" in Forager. Forager has 9 actions (including Get Work Email, Lookup a Person by Phone, and Lookup Personal Emails); JOOR has 52 actions (including Create Collections, Create Collections by Product External ID, and Create Line Items). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Forager-to-JOOR automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Forager (or JOOR) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Forager + JOOR automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Forager and JOOR integration.
- Forager and JOOR integration source code, module specs and credentials implementation.
- Our Forager and JOOR integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Forager and JOOR — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Forager integration information
- JOOR integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library