> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fentufsm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outbound Connections

> Configure outbound data synchronization from Fentu FSM to external systems

## Overview

Outbound connections push data FROM Fentu FSM TO external systems. This is typically used for sending completed work orders, time entries, material usage, and other transactional data to your ERP or CRM system.

<img src="https://mintcdn.com/fentu/VaII27VqRBHw2baV/images/fentu-connect/outbound/outbound-list.png?fit=max&auto=format&n=VaII27VqRBHw2baV&q=85&s=bee8b32e0b210ef7d906eb90b897ee08" alt="Outbound Connection List" width="1280" height="720" data-path="images/fentu-connect/outbound/outbound-list.png" />

## Outbound Connection List

The list displays all configured outbound connections:

| Column         | Description                                        |
| -------------- | -------------------------------------------------- |
| **Name**       | The display name of the outbound connection        |
| **Type**       | The external system type (e.g., SAP B1, Fentu-FSM) |
| **Object In**  | The source Connect Object from Fentu FSM           |
| **Object Out** | The destination object in the external system      |
| **Actions**    | Edit, configure, or delete the connection          |

### List Features

* **Search** - Filter connections by name
* **New Button** - Create a new outbound connection
* **Pagination** - Navigate through pages
* **Items per Page** - Choose display count

***

## Creating an Outbound Connection

<img src="https://mintcdn.com/fentu/VaII27VqRBHw2baV/images/fentu-connect/outbound/outbound-new.png?fit=max&auto=format&n=VaII27VqRBHw2baV&q=85&s=c7193a80377ebf7740195b5c0cf06b02" alt="New Outbound Connection Form" width="1280" height="720" data-path="images/fentu-connect/outbound/outbound-new.png" />

To create a new outbound connection:

1. Click **New** from the Outbound list
2. Enter a name for the connection
3. Select the system type
4. Configure the Active checkbox
5. Click **Save**

### Basic Fields

| Field      | Description                              | Required |
| ---------- | ---------------------------------------- | -------- |
| **Name**   | Display name for the outbound connection | Yes      |
| **Type**   | The external system type                 | Yes      |
| **Active** | Enable/disable synchronization           | No       |

### Available System Types

* **SAP B1** - SAP Business One
* **Fentu-FSM** - Another Fentu FSM instance
* **Salesforce** - Salesforce CRM
* **Acumatica** - Acumatica ERP
* **Shopware** - Shopware e-commerce
* **ABAS-ERP** - ABAS ERP
* **HRlab** - HR management
* **Window Maker** - Window manufacturing
* **Internal Connect** - Internal connections
* **Jsonblob Shopware** - Shopware via JSON

<Warning>
  Do not activate outbound connections until you have fully tested the configuration. Incorrectly configured outbound connections can create invalid records in your external systems.
</Warning>

***

## Outbound Connection Configuration

After creating the basic connection, edit it to configure:

### Connection Settings

| Field            | Description                                  |
| ---------------- | -------------------------------------------- |
| **Endpoint URL** | API endpoint for the external system         |
| **Credentials**  | Authentication fields (vary by system type)  |
| **Entity**       | The external system entity/table to write to |

### Object Mapping

| Field                 | Description                                            |
| --------------------- | ------------------------------------------------------ |
| **Object In**         | The source Connect Object from Fentu FSM               |
| **Primary Key Field** | The field used to match records in the external system |

### Field Mapping

Map Fentu FSM fields to external system fields using:

* **Field** - Direct field-to-field mapping
* **Raw Data** - Static values
* **Formula** - Calculated values using formula syntax

***

## Outbound vs Inbound: Key Differences

| Aspect           | Inbound                           | Outbound                               |
| ---------------- | --------------------------------- | -------------------------------------- |
| **Direction**    | External → Fentu FSM              | Fentu FSM → External                   |
| **Typical Data** | Master data (customers, products) | Transactional data (work orders, time) |
| **Trigger**      | Scheduled or manual               | Event-driven or scheduled              |
| **Primary Key**  | Matches external records          | Updates external records               |

***

## Common Outbound Use Cases

<AccordionGroup>
  <Accordion title="Work Order Completion to ERP" icon="check-circle">
    **Purpose:** Send completed work order data to your ERP for invoicing

    **Data typically includes:**

    * Work order ID and status
    * Labor hours and costs
    * Parts used
    * Customer information
    * Completion dates

    **Configuration tips:**

    * Map Fentu FSM work order fields to ERP sales order or service call fields
    * Include all required fields for ERP document creation
    * Use formulas to format data according to ERP requirements
  </Accordion>

  <Accordion title="Time Tracking Export" icon="clock">
    **Purpose:** Export technician time entries to payroll or billing systems

    **Data typically includes:**

    * Employee ID
    * Date and hours
    * Work order reference
    * Activity codes

    **Configuration tips:**

    * Ensure employee IDs match between systems
    * Format dates according to the target system's requirements
    * Include project/cost center codes if required
  </Accordion>

  <Accordion title="Inventory Updates" icon="boxes-stacked">
    **Purpose:** Sync inventory movements and usage to ERP

    **Data typically includes:**

    * Item codes
    * Quantities used
    * Warehouse locations
    * Work order reference

    **Configuration tips:**

    * Match item codes exactly between systems
    * Include warehouse/location information
    * Consider batch/serial number tracking requirements
  </Accordion>

  <Accordion title="Customer Updates" icon="user-pen">
    **Purpose:** Push customer information changes back to CRM/ERP

    **Data typically includes:**

    * Customer contact updates
    * Address changes
    * New site locations

    **Configuration tips:**

    * Only sync changed fields to avoid overwriting ERP master data
    * Use conditions to sync only approved changes
    * Maintain primary key consistency
  </Accordion>
</AccordionGroup>

***

## Best Practices

<AccordionGroup>
  <Accordion title="Validate Data Before Sending" icon="shield-check">
    Use conditions and formulas to validate data before sending to external systems. This prevents errors and rejected records.
  </Accordion>

  <Accordion title="Include Required Fields" icon="list-check">
    External systems often have required fields. Ensure all mandatory fields are mapped, even if they need default values.
  </Accordion>

  <Accordion title="Handle Errors Gracefully" icon="circle-exclamation">
    Configure error handling to prevent data loss. Failed outbound records should be logged for retry.
  </Accordion>

  <Accordion title="Test with Non-Production Data" icon="flask">
    Before activating outbound connections, test with sandbox/development environments to verify records are created correctly.
  </Accordion>

  <Accordion title="Use Conditions to Filter" icon="filter">
    Only send records that meet specific criteria (e.g., status = 'completed', type = 'billable') to avoid sending incomplete data.
  </Accordion>
</AccordionGroup>

***

## Common Questions

<AccordionGroup>
  <Accordion title="When is outbound data sent?" icon="question">
    Outbound sync can be triggered by:

    * Scheduled intervals
    * Record status changes (e.g., work order completion)
    * Manual trigger
      Check with your administrator for the specific configuration.
  </Accordion>

  <Accordion title="What if the external system is down?" icon="question">
    Failed outbound attempts are typically queued for retry. Check the sync logs for failed records and their error messages.
  </Accordion>

  <Accordion title="Can I send partial updates?" icon="question">
    Yes, you can configure outbound connections to only send specific fields rather than the entire record. This is useful for updating just status fields or specific attributes.
  </Accordion>

  <Accordion title="How do I handle record creation vs updates?" icon="question">
    The Primary Key Field determines whether to create or update:

    * If a matching record exists in the external system, it's updated
    * If no match exists, a new record is created
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Records Not Sent" icon="circle-exclamation">
    **Check:**

    * Is the connection Active?
    * Do records meet the condition criteria?
    * Are connection credentials valid?
    * Is the sync schedule running?
  </Accordion>

  <Accordion title="Records Rejected by External System" icon="ban">
    **Common causes:**

    * Missing required fields
    * Invalid data format
    * Duplicate key errors
    * Validation rule failures

    **Solution:**

    * Review error messages in sync logs
    * Verify field mappings include all required fields
    * Use formulas to format data correctly
  </Accordion>

  <Accordion title="Wrong Data Sent" icon="triangle-exclamation">
    **Check:**

    * Field mapping configuration
    * Formula syntax for calculated fields
    * Source field names match expected values
  </Accordion>
</AccordionGroup>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Inbound Connections" icon="arrow-down" href="/fentu-connect/inbound">
    Configure inbound data pull from external systems
  </Card>

  <Card title="Connect Objects" icon="cube" href="/fentu-connect/connect-objects">
    Define data structures for integration
  </Card>

  <Card title="Formula Reference" icon="function" href="/fentu-connect/formula-reference">
    Learn formula syntax for data transformation
  </Card>

  <Card title="Connection Config" icon="gear" href="/fentu-connect/connection-config">
    Configure connection credentials
  </Card>
</CardGroup>