One of the benefits of GUIDEcx is that our system easily integrates with applications your company or even the client you are onboarding is currently using. To make the process as seamless as possible, we offer three different ways to integrate applications.
A native integration is when an application is built natively into a SaaS platform. This platform houses the connection between the two softwares. Native integrations are great because they’re usually ready-to-use and often require less or no code.
Although they have some great benefits, they’re not perfect. Here are some disadvantages to using native integrations:
- There are limitations: Native integrations need to support the most common use cases in order to provide value to the largest number of customers. Those use cases may not always align with your use case.
- Not scalable: As your business grows, your integrations will have to expand as well. This can be more difficult with native integrations.
Because of these disadvantages, we use Zapier and our open API to access the full functionality of these native integrations.
GUIDEcx has four main native integrations:
- Jira Software
Why these applications? Well, they’re the ones our customers want to integrate the most with. But half of them help with the sales handoff.
For example, Salesforce and HubSpot keep your sales team organized. When you integrate them with GUIDEcx, you can automatically start a new onboarding project that transfers notes, contacts, and automatically invites the new customers.
However, these are native because we want you to be able to customize that transfer to how your organization functions.
Zapier is how these non-native integrations get even more customization.
For example, we use Zapier webhooks to enhance our HubSpot and Salesforce integrations. This helps make sure everything that can be automated is automated.
Zapier allows for other integrations, including those not listed above. Whether you want to enhance a non-native integration or create a new one, Zapier is the perfect tool.
When you have access to developer resources, you can create a custom integration with the GUIDEcx API, which is based on the Open API specification. This allows you to tailor the experience for your specific business needs, avoiding any potential disadvantages of a native integration.
Not only do we use Zapier to expand our HubSpot integration, but we use our open API as well. The concept is the same as Zapier, where you can enhance a current integration or create a new one, but with the open API, you can be much more specific.
An open API (application programming interface) is how you can really expand your tech stack. The possibilities are literally endless.
Open APIs are easy to implement (if you know how) and cost effective. Greater functionality for less money. Isn’t that the dream?