Sending Your Data to SyncHive

This page explains how to bring data from an external system into SyncHive for the first time.
It walks through the process of identifying your external data, selecting the right shape in SyncHive, setting up your Connector and Integration, and finally verifying that the data arrives correctly.

An inbound data flow exchanges data from an external system via a shape in SyncHive. It defines how data is imported, validated, and structured within the platform.

For example, a low-code application might need to display real-time sales and billing data from multiple external systems, including HubSpot. SyncHive acts as the data backbone that connects these systems, aligns their structures, and provides a unified data layer to the low-code app.

1. Identify the External System and Data Model

Start by deciding which system you want to integrate and what data you need from it.

1. Choose your external system (in this example, HubSpot).

2. Determine the data model you want to sync, for instance:

• Customers and contacts (CRM)

• Invoices or payments (Billing)

• Orders or products (Commerce)

3. Review how that data is represented in the source system: property names, data types, and identifiers.

4. Identify any required fields that must exist in SyncHive (for example, customer email or invoice ID).

Tip: Start with a single entity, such as Customer or BillingDocument, to simplify initial validation.

2. Select or Create the Shape in SyncHive

Next, locate or create the shape in SyncHive that will receive your data.

1. Navigate to Explore → Shapes.

2. Browse existing shapes that match your external data model.

For example, Customer, SalesOrder, or BillingDocument.

3. If none fit closely, click New Shape to create one - see Managing Shapes for step-by-steps instructions.

4. Review and adjust:

• Property names and types

• Descriptions and groupings

• Required versus optional fields

5. Use Pick Properties to reveal optional fields before adding new ones.

6. When finished, click Publish to save your changes as a new shape version.

Note: Shapes define the structure SyncHive expects when data arrives. Ensuring alignment here simplifies all later steps.

3. Add a Connector

A Connector defines how SyncHive communicates with your external system. It contains connection settings and supported data shapes.

1. Navigate to Integrate → Connectors.

2. Click Add Connector to open the wizard.

3. Fill in required fields:

• Name – descriptive (e.g. HubSpotConnector1)

• Key – a unique identifier (e.g. hubspotC1)

• Shape – the shape that will receive the data (e.g. Product)

• Version – start with 1.0.0

• Status – set to Enabled

4. Choose an External Contact Type appropriate for the source you want to integrate with.

5. Link the Connector to one or more shapes that represent the data you plan to send. (Optional when adding a connector as it can be done later)

6. Click Save to create the Connector.

4. Create an Integration

An Integration links a specific instance of your external system (for example, a particular HubSpot account or Stripe workspace) to the Connector you just added.

1. Go to Integrate → Integrations.

2. Click Add Integration.

3. Complete the form:

Name – clear label (e.g. Hubspot)

Key – unique identifier (e.g. H1)

Connector Key – choose the Connector created in the previous step.

Status – set to Enabled.

Version – version number such as 1.0.0.

Tenant ID – optional ID for your system instance if required.

4. Assign the relevant shape (e.g. Customer).

5. Review the inbound configuration, including event triggers or schedule type (event-based or polling).

6. Save the Integration.

At this point, SyncHive knows which system to connect to (via the Connector) and how to structure its data (via the Shape).

Note: Each integration corresponds to a single system instance (for example, one HubSpot workspace or one Stripe account).

5. Review Configuration and Enable the Flow

Before sending any data, check all configuration details:

• The Connector and Integration are both set to Enabled.

• The Shape used by the integration matches your external data model.

• Authentication credentials are valid and have sufficient permissions.

• Any inbound flow parameters (frequency, event types, or filters) are defined.

Once confirmed, enable the inbound flow in the Integration screen.

6. Send Data from the External System

When the configuration is complete, send a small test batch of data from your external system.

• For event-based systems (like HubSpot or Stripe), trigger a small update or create a new record.

• For file-based or database integrations, initiate a single import or synchronization job.

The data will flow through the Connector, into the Integration, and appear in SyncHive under the associated shape.

Tip: Start with a minimal dataset to verify field mappings before scaling up.

7. Monitor and Validate

After sending data, use SyncHive’s monitoring tools to confirm successful processing.

1. Open Dashboard.

2. Check the message synching status for your integration.

3. Review:

• Message counts and processing status.

• Any validation or mapping errors.

• Message logs

• Stuck messages

4. Go to Explore and confirm that the new records appear under the correct shape with accurate field values.

If data appears as expected and no errors are shown, your first inbound flow is successfully established.

8. Common Setup Issues

Issue	Description	Resolution
Shape mismatch	Data from the external system doesn’t match the selected shape.	Adjust the shape or mappings to align field names and types.
Disabled flow	Messages are not processed.	Verify that both the Connector and Integration are enabled.
Invalid credentials	SyncHive can’t authenticate with the source.	Recheck API tokens or connection permissions.
Unmapped identifiers	Records appear as duplicates or fail validation (check ID Resolution.).	Ensure a unique ID (such as Customer ID or Invoice ID) is included.

|

9. Next Steps

After confirming your first data flow:

• Add additional shapes for related entities.

• Configure outbound flows to push data back into external systems.

• Enable event sourcing.

• Use the unified data in external systems, such as Power Apps, Retool, or other automation tools.

• Connect AI agents or automation workflows to use structured SyncHive data.