Jitterbit EDI AI Assistant

Introduction

The EDI AI Assistant streamlines the management and configuration of Jitterbit EDI by interacting with it using written natural language.

Access the EDI AI Assistant

Access the assistant from these places:

• In the Harmony portal header on any Jitterbit EDI page, use the Jitterbit AI icon. In the panel, use the dropdown to select EDI AI Assistant.

• From these Jitterbit EDI pages:

  • On the Trading Partners page, click New > Build with AI.

  • On a trading partner's Manage workflows tab, click New > Build with AI.

  • On a trading partner's Communication settings tab, click New > Build with AI.

  • On the Transactions page, click Search > Search with AI in the advanced search builder.

The Build with AI and Search with AI options are visible to all users, whether or not their Harmony license includes the EDI AI Assistant option:

• If your license includes the EDI AI Assistant option, selecting one of these options opens the assistant.

• If your license doesn't include the EDI AI Assistant option, selecting one of these options opens a dialog describing the assistant, with a contact form. Submitting the form sends a request for it to be added to your license.

EDI AI Assistant controls

The EDI AI Assistant panel includes these controls:

• New chat: Start a new chat.
• Expand: Expands the chat. Once expanded, click the Minimize icon to return to the previous view.
• Resize: Drag the left edge of the panel to adjust its width.

Supported interactions and capabilities

The following interactions and capabilities are supported.

Trading partner

The EDI AI Assistant can help you with managing your trading partners:

• Communication: Create and edit new AS2 and FTP communication connections, and modify and view connection details such as name, address, port, login, frequency, and active status.

  Warning

  Do not include FTP or AS2 certificate passwords in your prompts. Providing them will not work and unnecessarily exposes your sensitive data to the model.

• Workflows: Create and edit EDI XML workflows, and view EDI XML workflow details such as map processing, direction, EDI standard, document type, and version, and ACK and debug settings.

• Trading partners: Create and update trading partners, supporting both mandatory fields and optional configurations like archive settings.

• Settings: Retrieve and query EDI configuration settings for IDs (including preferred partner ID and your preferred ID), and the connection type, name, and frequency.

Transactions

The EDI AI Assistant supports querying and filtering of transactions.

Wherever a transaction search supports a document type filter, you can filter by either of the following:

• A general document type (such as Invoice or Order) returns all documents of that type, across all of its document type codes.

• A specific document type code (such as 810, 850, ORDERS, or INVOIC) returns only documents of that subtype. You can refer to a subtype by its code alone (for example, 810) or by the code qualified with its general type (for example, Invoice.810, Order.850, or Invoice.INVOIC).

The following interactions are supported:

• Filters: Query and retrieve data using various combinations of direction, status, trading partner, document type (general type or specific code), date range, and document ID. When matching documents are found, the assistant summarizes them and asks you to confirm before showing the results:

  • If 25 or fewer matching documents are found, the assistant displays them and opens or refreshes the Transactions page to show the filtered results in the transactions table.

  • If more than 25 matching documents are found, the assistant displays the first 25 and asks whether you want to see the remaining documents. The results appear in the AI chat panel only, and the Transactions page is not opened or refreshed.

  Example user prompts

  • How many orders did Walmart US send today?
  • List all my invoices.
  • List all my 880 invoices.
  • Show all Order.850 documents for partner 3M.
  • Show all POs from Lowe's.
  • Show any errors from Lowe's.
  • Filter by order and Walmart for the last month.
  • Are there any errors this morning?
  • Show me any of my orders that didn't download.

• Non-acknowledged documents: Search for outbound documents that are missing expected acknowledgments. The assistant cross-references your workflow configurations to determine which document types require acknowledgments, then searches for documents where the Acknowledged By field is null. You can optionally filter results by partner name, document type (general type or specific code), date range, or custom fields including document ID, control numbers (ISA, GS, ST), document dates, and user-defined fields (UDF1–UDF5). Results appear in the AI chat panel only:

  • If 10 or fewer matching documents are found, the assistant lists the document IDs.
  • If more than 10 matching documents are found, the assistant reports the total count and offers to summarize results grouped by partner name.

  Example user prompts

  • Show non-ack documents.
  • Find non-ack documents for partner CommerceHub Amazon Marketplace.
  • Find non-acknowledged documents between April 1 and April 30 2026.
  • Show non-ack documents for the last 7 days.
  • Find non-ack documents with doc type 810.

• Acknowledged documents: Search for documents that have been acknowledged. You can optionally filter results by partner name, document type (general type or specific code), date range, or custom fields including document ID, control numbers (ISA, GS, ST), document dates, and user-defined fields (UDF1–UDF5). Results, including the total number of matching documents found, appear in the AI chat panel only. After retrieving acknowledged documents, you can ask the assistant to calculate the average acknowledgment time overall or by document type.

  Example user prompts

  • Show acknowledged documents for partner 3M.
  • Find acknowledged 810 invoices from the last 30 days.
  • What is the average time to acknowledge documents?
  • What is the average acknowledgment time for orders?

• Non-compliant documents: Search for documents that failed compliance checks. You can optionally filter results by partner name, document type (general type or specific code), direction (inbound/outbound), status (Success, Error, Pending, and others), or date range. Results appear in the AI chat panel only:

  • If 20 or fewer matching documents are found, the assistant lists the document IDs.
  • If more than 20 matching documents are found, the assistant asks whether you want to group results by partner or refine your search criteria. Grouping by partner returns counts per partner without individual document IDs.

  Example user prompts

  • Show non-compliant documents.
  • Show non-compliant documents for partner 3PL Central.
  • Show non-compliant documents created after March 1, 2026.
  • Show non-compliant invoice documents for partner 3M in the last month.
  • Show non-compliant 810 documents for partner 3M.

• Resend acknowledgements: Ask the assistant to send or resend acknowledgements for inbound transactions. The assistant searches for matching inbound documents and asks for your confirmation before sending any acknowledgements. If you decline, no acknowledgements are sent. You can optionally filter by partner name, document type (general type or specific code), status (such as Success, Error, or Pending), date range, or the same custom fields supported for other transaction searches. Results appear in the AI chat panel only.

  Example user prompts

  • Resend acknowledgements for Walmart US transactions from last week.
  • Send acknowledgements for all pending inbound 850 documents from Lowe's.

• Reprocess transactions: Search for documents matching optional filter criteria and reprocess them after explicit user confirmation. You can filter by partner name, document type (general type or specific code), direction (inbound/outbound), status (Success, Error, Pending, and others), date range, or the same custom fields supported for other transaction searches. If no criteria are provided, the assistant searches all available documents. The assistant presents matching results and asks for confirmation before reprocessing begins. If you decline, no documents are reprocessed. Results appear in the AI chat panel only.

  Example user prompts

  • Reprocess the document with ID 12345.
  • Reprocess all error documents from Walmart for today.
  • Reprocess all error 810 documents from Walmart for today.

• Archive transactions: Search for documents matching optional filter criteria and archive them after explicit user confirmation. You can filter by partner name, document type (general type or specific code), direction (inbound/outbound), status (Success, Error, Pending, and others), date range, or the same custom fields supported for other transaction searches. If no criteria are provided, the assistant searches all available documents. The assistant presents the number of matching documents and asks for confirmation before archiving begins. If you decline, no documents are archived.

  Example user prompts

  • Archive documents with document ID VA-Shipment-008.
  • Archive documents for partner 3M.
  • Archive documents with document type Order.
  • Archive documents with document type 880.
  • Archive documents created after March 1, 2026.

• PII guidance: The EDI AI Assistant answers questions about PII fields and masked data in documents, and provides a link to the Enable PII documentation. The assistant provides guidance only and does not query or expose actual PII data.

Messages

The EDI AI Assistant allows for filtering and advanced queries of messages:

• Filters: Filter messages based on error, trading partner, date range, or keyword.

• Advanced queries: Perform more advanced queries, allowing the large language model (LLM) to determine results based on the query.

Analytics

The EDI AI Assistant provides search capabilities for analytics:

• Search capability: Perform searches based on date, trading partner, or document type.

• Total/sum queries: Navigate to the Transaction volume report when you request totals or sums.

Recommendations

You should interact with the EDI AI Assistant as you would with any large language model (LLM) AI product. Follow these suggestions:

• Write in English using whatever wording comes naturally to you, as if talking to a person with your own level of IT and business knowledge. Other languages may be used but have not been validated.

• To get ideas of what interactions you can perform, ask the assistant in natural language what it can do, or type help.

• Read the assistant's responses carefully before typing your reply. If there's something you don't understand, ask the assistant to clarify.

• Once the assistant has performed an action, you can review and confirm what it did by browsing the configuration in the UI. If any settings are not as expected, you can ask the assistant to edit them or edit them directly.

Limitations

The following interactions are not yet supported:

• Trading partner

  • Delete, import, or export trading partners.

  • Add or assign a company ID.

  • Delete workflows.

  • Delete or assign communication settings.

  • View, create, or update FTP or AS2 certificate passwords.

  • Edit, add, or remove labels.

  • Edit, add, or remove custom fields.

  • Manage transactions.

• Transactions

  • Direct query of transaction details. The assistant can navigate to specific transaction tables (for example: Show me Walmart orders), but it cannot extract specific data points within those transactions, such as PO numbers or received times.

  • Query personally identifiable information (PII).

  • Change the order or viewing of columns or sort columns.

  • Refresh the screen.

  • Upload an EDI file.

  • Specify multiple document IDs in a single search, reprocess, resend acknowledgements, or archive request. (A search request that includes multiple document IDs returns no documents.)

  • Print, copy, or save a transaction from the raw view.

• Archive

  • Query archived transactions.

• Analytics

  • Export reports upon request.