Hi, how can we help you today?

This knowledge base will guide you through all the necessary steps to help shape the future of our product.

Managing Integrations: Why "App X" and "App Y" Don't Always Talk

Introduction

The most frequent requests we receive are for integrations: "Can you sync with Slack?" or "Can we get a Salesforce plugin?" While we want our tool to sit at the center of your workflow, building an integration is a "two-way street" that we don't always fully control.

The Challenge of Third-Party APIs

To "talk" to another software, we use something called an API (Application Programming Interface). Think of this as a door that the other company leaves open for us. However:

  • The Door Might Be Locked: Some companies charge massive fees for API access or limit what data we can "see."

  • The Door Might Move: If the other company updates their software, they might change their API without telling us, causing the integration to break.

Security and Privacy Compliance

When we build an integration, we are effectively creating a bridge for your data to travel across. Before we launch any connection, our legal and security teams must ensure that the other company meets our high standards for data encryption. If we feel that connecting to another app puts your data at risk, we will decline the integration.

What You Can Do to Help

If you want an integration between us and another tool, reach out to the other company as well. When both companies hear from the same users, it creates a "partnership" opportunity. This makes it much easier for our engineers to get the technical documentation and support they need to build a stable, long-lasting connection.