Integrations

TriggerMesh Bridges

Compose Bridges out of one or more Sources, a Broker that provides event routing, filtering, transformation, and splitting, and one or more Targets.

Build Cloud Native Integrations

Automate Workflows

Connect event Sources and Targets through Brokers – we call these connections Bridges. They can be assembled using any combination of Sources, Brokers, and Targets, giving you infinite flexibility

Sources

Events are changes that happen within a system. These changes are captured via a message and forwarded from event sources

Integrate with existing sources or register your own
AWS Code Commint
AWS Cognito Identity
AWS Cognito User Pool
AWS Dynamo DB
AWS S3
AWS SNS
AWS SQS
Amazon Kinesis
Azure Activity Logs
Azure Blob Storage
Azure Event Hubs
Google PubSub
Google Storage
HTTP Poller
Microsoft Active Directory
OCIMetrics
OracleDB
Salesforce
Schedule Functions
Slack
VMware Vsphere
Webhooks
Zendesk

Brokers

Brokers perform event routing, event transformation, and event store

Select a service to connect Sources with Targets
AWS Kinesis
Apache Kafka
Azure Event Hubs

Targets

Targets (aka Sinks) listen for and consume events

Use existing targets or register your own
AWS EventBridge
AWS S3
Amazon Kinesis
Amazon Lambda
Amazon SNS
Amazon SQS
Confluent
Datadog
Elasticsearch
Google Sheets
HTTP
Hasura
InfraJS
Knative
Kubernetes
Logz.io
OpenShift Serverless
OracleDB
Salesforce
SendGrid
Slack
Splunk
Tekton
Twilio
Zendesk

How TriggerMesh Differs

TriggerMesh sits at the nexus of cloud and legacy applications

Join our newsletter

Sign up for our newsletter for the latest news, training, and offers to help you build event-driven systems with TriggerMesh.