1. Options to send data to Gundi for transformation, processing, and delivery

Objective: Establish a Gundi inbound connection. 

1.1 Gundi Webhook

• For sources with support for webhooks, this is often the simplest integration method. 
• Depending on the complexity and structure of the data, some integrations can be handled through configuration alone, while others may require coordination with our development team.
• If this option interests you, please contact our team sharing the following information.

1.2 Gundi API

• Gundi's API gives developers full control over their integration, and typically requires minimal coordination with our team. 
• Online documentation here.
• If you are interested in this option, please share the following:

1.3 Custom Gundi Integrations  

• When a system cannot push data, our team can build a Connector to pull data from that system's API. 
• These integrations are often developed with a scheduled polling mechanism (e.g., every 5–30 minutes).
• This option requires coordination with our development team. Timelines will depend on implementation complexity and team availability.
• If you are interested in this option, please share:

2. Options to receive data from Gundi

Objective: Establish a Gundi outbound connection.

2.1 Custom Gundi Integrations

• Our team can build a custom Connector to push data to your system.
• The process involves understanding your system, user requirements, and API.
• If you are interested in this option, please share:

3. Collaboration

Once you have selected your preferred approach, please contact our team and share relevant details, including:

• Technology name and description
• Desired outcomes
• Technical point of contact
• Relevant device and/or integration specifications