System

What Is a System?

A System is a business application, platform, software service, or operational tool that stores or exchanges business information. When you add a System to a SeekBytes Project, it becomes part of the network and can be connected to other project components.

Examples of Systems include:

• ERP systems (SAP, Oracle)
• CRM systems (Salesforce, HubSpot)
• E-commerce platforms (Shopify, WooCommerce)
• Inventory and field service tools
• Payroll and accounting systems
• Booking platforms and support portals
• Custom APIs and AI services

Why Does This Term Matter?

Most business value comes from connecting real systems. People don't usually automate for the sake of automation — they automate because real business applications need to share data and trigger actions. The System is the real-world application side of the story.

What Happens When You Add a System?

When you add a System to a Project, you're telling the platform:

• This business application matters to this Project
• It needs to participate in data exchange or process flow
• It may need Connectors, configurations, and Automations around it

The System becomes an Entity in the project network — a recognized participant that other components can interact with.

Real-World Example

The IT team uses ServiceNow for incident management, Jira for change tracking, and a monitoring platform for infrastructure health. Each of these is a System. They are separate business tools, but in SeekBytes they can be represented in the same Project and connected together through Connectors and Connections.

What a System Is Not

A System is not the whole Tenant (that's the organization). A System is not the Connector itself (that's the bridge). A System is not the Runtime Identity (that's the security credential). A System is the real-world application being represented in your project.