Integrations

Twinfinity does not have to be an island. When something changes in your tenant — an issue is raised, a twin is updated — Twinfinity can push an event to your own infrastructure, and your code can call back into the Twinfinity API to read whatever extra detail it needs. Together those two capabilities let you keep an external system in sync with Twinfinity in near real-time.

This area covers how to build those integrations as a developer: what events look like, how to receive them, and how to authenticate a back-end service or serverless function so it can read from the API.

What you can build today

React to changes. Subscribe to events about issues and twins and have your own code run whenever they change.
Sync to external systems. Forward those changes to a CRM, a data warehouse, a ticketing system — wherever the data needs to go.
Read more from the API. Events carry a compact payload; your service authenticates as a machine-to-machine client and fetches the full picture over the REST API.
Run logic inside the twin pipeline. For processing that should become part of the twin itself, Twinfinity can run a customer-specific processor on your behalf.

How it fits together

Something changes in Twinfinity (issue, twin, ...)
        │
        ▼
Twinfinity forwards a CloudEvent  ──►  your Azure Service Bus queue / topic
                                            │
                                            ▼
                                   your Azure Function / AWS Lambda
                                            │  (authenticates with an OAuth client id + secret)
                                            ▼
                                   reads extra detail from the Twinfinity REST API
                                            │
                                            ▼
                                   writes it to your external system

Getting set up is a provisioning step. Event forwarding to your Service Bus, and the OAuth client (client id + secret) your service uses to call back, are configured per tenant by Twinfinity together with your administrator. This area documents how to consume the integration once those are in place — talk to your Twinfinity contact to have them provisioned.

Where to go next

Syncing data to external systems with events — receive events from Azure Service Bus and call back into the API.
Customer-specific twin processors — run your own logic inside the twin processing pipeline (managed capability).