Connectors 101
What are Connectors? A connector serves as an integral component within an integration, allowing Pandium to securely provide the required encrypted secrets or tokens to the specific integration and tenant combination. Pandium's connectors are designed to accommodate the authentication requirements of partner systems, whether that involves an OAuth protocol, a simple API key, or a custom and proprietary method.
In contrast to many integration platforms, Pandium’s connectors focus solely on authorization, authentication, and receiving webhooks. It's important to note that Pandium's connectors refrain from interacting with external APIs beyond these essential functions. As such, there is no “Pandium version” or “wrapper” around third-party APIs.
Connector Secrets?
When an integration script runs on the platform, it dynamically accepts the necessary secrets as environment variables at runtime. These secrets are encrypted at rest and in transit, and cannot be exported.
For a given integration, connectors can be set on a per-tenant basis or globally. This global configuration is particularly useful when one facet of the integration remains static, such as utilizing a uniform SFTP or cloud storage bucket for all customer accounts. Opting for a global connector implies that authentication into the system is required only once. Subsequently, all created tenants will share the same set of global secrets, eliminating the need for redundant authentication.
Pandium connections can be diverse - we don't need to connect to a public API to work. Whether it's through public or private APIs (leveraging a direct AWS/GCP/Azure connection), SFTP, Storage Buckets, or even direct database connections, Pandium adapts seamlessly, provided the necessary access is available.
How many native connectors does Pandium Support?
210! That's a lot of connections; for a full list, please see here. We are always evolving as your business grows, so if there is an integration that your tech stack requires and you do not see a connector for it, please reach out to your Technical Account Manager about getting one built on your timeline at no additional cost. For setup configuration guides, please refer to the linked sub-pages for our existing connectors.
How do your connectors differ from one another? They don't because we don't wrap the API. Our connectors only operate as an authentication management tool. The only difference between connectors is how the SaaS provider authenticates their respective API.
Last updated
Was this helpful?