Connectors Bundle SaaS

This application is a collection of pre-built tools that allow your automation processes to talk to popular web services like Slack or Google Drive.

  • Home Automation
This application is a collection of pre-built tools that allow your automation processes to talk to popular web services like Slack or Google Drive. It saves time by providing ready-made links to external software, meaning your team doesn't have to write custom code for every integration.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

59/100 Fair

Maintained
100last commit 16 days ago
Popular
3772 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
206 GB minimum RAM, runs on ARM
Security check
70no serious findings, 10 minor, CI, tests
GitHub stars
72
Open issues
225
Last commit
2026-11-05
Latest release
8.10.4
Activity
rising

Checked 16 days ago - source: GitHub (camunda/connectors)

Resources & Compatibility

Minimum requirements: 6 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set real AlloyDB login and SSH details Replace the sample database address, password, SSH endpoint, and SSH private key (a secret file that lets the connector use a secure tunnel) with your own values. If you leave dummy values or share that key, the connector may fail to write to your database or expose access to it. source
  • Add Gong API keys, region, and start date Put your Gong access key and secret (the login credentials for the Gong API), the correct region, and a start date into the capture config before starting the connector. Without those, the connector cannot sign in to Gong or know which calls, users, and scorecards to pull. source
  • Point Kafka config at your server Change bootstrap_servers (the address the connector uses to find your Kafka message system) to your actual Kafka address. If it is wrong or still points to a local test server, the connector will not find the messages it is supposed to read. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I connect a locally run connector runtime to a Camunda SaaS cluster?

Review the hybrid mode guide for connecting a local connector runtime to a SaaS cluster.

What does the Connectors Bundle Docker image provide?

It provides the Connector Runtime and all out-of-the-box Camunda connectors in an image that starts the Connector Runtime. It is intended for local setup or Kubernetes.

Which configuration areas should I review when deploying connectors for self-managed or SaaS use?

Review application properties, security settings, secret management, and development-specific configurations. These options are documented for self-managed and SaaS deployment scenarios.

Answers sourced from deepwiki.com, docs.camunda.io, github.com

Community

Collected 48 days ago - public community threads