The Home module is the central entry point in OneEnterprise. When you log in, you get a consolidated view of your entire integration environment — so you can manage entities, configure integrations, and monitor workflows from a single location, without switching between separate tools. The Home module is organized into seven areas:
The Dashboard gives you a real-time view of your integration environment as soon as you log in. It surfaces the status of active workflows, recent execution results, connection health, and any errors or warnings that require your attention — all in one place.
Business Partner
The Business Partner area is the registry of external organizations and service providers that you integrate with through OneEnterprise. A business partner is any business entity — a customer, supplier, logistics provider, or technology vendor — that connects to your integration environment to exchange data or participate in automated workflows.
What a Business Partner Represents
Each business partner record in OneEnterprise holds the organization's identity, integration role, and connection details. OneEnterprise uses this record to route data correctly across integrations and to apply the right authentication and mapping rules when communicating with that partner's systems.
Key Actions
- Add a new business partner and define its name, type, and role in your integration ecosystem.
- Configure partner-specific authentication and endpoint details.
- Link contacts to a business partner to track the individuals involved.
- Associate connectors and automations with a business partner to manage all related integrations in one view.
- Deactivate or archive business partners that are no longer active.
Contacts are the individual people associated with your business partners or your own organization. The Contacts area lets you maintain a directory of key personnel — technical contacts, account managers, and operational staff — who are involved in your integration projects and workflows.
Integration workflows often require person-level context — for example, knowing which account manager to notify when a transaction fails, or which technical contact to reach when a partner's system is unreachable. Contacts in OneEnterprise give your automations and workflows a way to reference real individuals and trigger appropriate communications.
Key Actions
- Add a new contact and associate them with a business partner or internal team.
- Record contact details, including name, role, email address, and phone number.
- Update contact information when personnel changes.
- View all contacts linked to a specific business partner from the Business Partner record.
Projects
Projects provide a structured workspace for organizing your integration work. Each project groups the automations, connectors, and assets that belong to a specific integration initiative, business domain, or team — so you can manage them together and track progress in one place.
Why use Projects
When your organization runs multiple integrations simultaneously — for example, an ERP-to-CRM sync alongside a separate logistics feed — Projects keep each initiative separate, auditable, and easy to hand over. You can assign ownership, set permissions, and track the lifecycle of each integration from build to production.
Key Actions
- Create a new project and define its name, description, and owner.
- Add automations and connectors to an existing project.
- Review project-level activity logs and execution history.
- Archive projects that have reached the end of life.
Connector
Connectors are the configured system links that enable OneEnterprise to exchange data with your external platforms — ERP systems, CRMs, databases, cloud services, and any other application involved in your integrations. Each connector stores the authentication credentials, endpoint configuration, and protocol settings required to communicate with a specific system.
How Connectors Work
You define a connector once and reuse it across any number of automations and projects. This means that when credentials change — for example, an API key is rotated — you update the connector in one place, and every automation using it automatically picks up the change.
Supported Connection Types
OneEnterprise supports a range of protocols and authentication methods to suit different integration patterns, including:
- HTTP / REST — for API-based integrations with web services.
- Basic authentication — for systems using username and password credentials.
- Synchronous connections — for integrations require an immediate response from the target system.
- Asynchronous / queue-based — for message-driven architectures where responses are handled independently.
- Subscription-based — for event-driven integrations that listen for changes in a connected system.
Key Actions
- Add a new connector and configure its endpoint, authentication, and protocol settings.
- Test a connector to verify that OneEnterprise can reach the target system.
- Activate a connector to make it available for use in automation.
- Update connector credentials without affecting the automations that depend on it.
Automations
Automation is the workflows that execute your integrations. Each automation defines a trigger — the event or condition that starts the workflow — and a sequence of steps that run in response. Once active, automation runs without manual intervention, ensuring your integration processes execute reliably and on time.
Trigger Types
OneEnterprise supports four trigger types to cover different integration patterns:
- HTTP Call — activates the automation when an incoming HTTP request is received. Use webhooks and API-initiated integrations.
- Queue — activates the automation when a message or task is added to a queue. Use for real-time, message-driven data processing.
- Subscriber — activates the automation when a specific event occurs in a subscribed system. Use for event-driven workflows that react to changes in connected platforms.
- Timer — activates the automation on a set schedule or interval. Use for batch processes, periodic syncs, and time-based workflows.
Automation Lifecycle
An automation moves through the following states:
- Draft — the automation is in design and not yet active.
- Active — the automation is live and responds to its trigger.
- Paused — the automation is temporarily suspended without losing its configuration.
- Archived — the automation is decommissioned and removed from the active list.
The Automations list shows each automation's name, trigger type, associated connector, and current status. Select an automation to view its configuration, execution history, and error logs.
On-Premise Agent
The On-Premise Agent is a lightweight software component you install within your own infrastructure. It creates a secure, outbound-only channel between your on-premise systems — such as local ERP installations, databases, or legacy applications — and the OneEnterprise cloud platform, without requiring inbound firewall rules or VPN configuration.
When to use the On-Premise Agent
Use the On-Premise Agent when you need to integrate systems that are not publicly accessible — for example, an SAP instance running inside your corporate network, or a proprietary database hosted in your data center. The agent acts as a relay: OneEnterprise sends instructions to the agent, the agent communicates with your on-premise system, and it returns the results securely to the platform.
Key Actions
- Download and install the agent on a server within your on-premise environment.
- Register the agent with your OneEnterprise tenant to establish a trusted connection.
- Associate the agent with the connectors that target on-premise systems.
- Monitor agent status and connectivity from the Home module.
- Update or restart the agent when maintenance is required.
Use the following Knowledge Base articles for detailed guidance on each area of the Home module: