Brandon Fu
Appearances
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
Yeah, so there's a lot here and I think there's a lot of aspects to the different problems that you have to solve in the integration story in building these integrations and also providing them in a user-friendly way for your customers to self-serve and onboard and consume those integrations. So part of what the Paragon SDK provides is that embedded user experience.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
Again, what we call our connect portal. That's going to provide the authentication for your users to connect their accounts. That's going to be the initial onboarding. But in addition to that, your users may also want to configure different options or settings for their integrations.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
A common example that we see for Salesforce or for CRM integrations in general is that your users may want to select some type of custom object mapping. Every CRM can be configured differently. So your users might want to map objects to some different type of record in their Salesforce or different fields in their Salesforce.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
And typically that's what developers would have to build on their own is this UI for your users to configure these different settings for every single integration.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
That's also going to be what's provided by the Paragon SDK is not just that initial onboarding and authentication experience, but also the configuration end user UX for different settings like custom field mapping, selecting which types of features on your integration that your user might want to configure. And that's also going to be provided fully out of the box by Paragon SDK.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
With integrations, different APIs might have different rate limits. They might have different policies that you have to conform with. And your developers typically have to learn these different nuances for every API and write code individually to conform to those different nuances.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
With Paragon, because we build and maintain the connector with each of the integrations that we support in our catalog, we're automatically going to handle for things like retries, things like rate limits.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
For example, Paragon knows the rate limit for each provider and will automatically throttle your requests so that you can conform to the rate limit for those providers and be able to intelligently retry requests in the events that you exceed the rate limit or a request fails.
The Changelog: Software Development, Open Source
Building customizable ergonomic keyboards (Interview)
And so we look at this as sort of the backend or infrastructure layer of the integration problem that we have spent the last five years essentially building and optimizing the Paragon infrastructure to act as the integration infrastructure for your application.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
Yeah, so there's a lot here, and I think there's a lot of aspects to the different problems that you have to solve in the integration story in building these integrations and also providing them in a user-friendly way for your customers to self-serve and onboard and consume those integrations.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
So part of what the Paragon SDK provides is that embedded user experience, again, what we call our Connect Portal. That's going to provide the authentication for your users to connect their accounts. That's going to be the initial onboarding. But in addition to that, your users may also want to configure different options or settings for their integrations.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
A common example that we see for Salesforce or for CRM integrations in general is that your users may want to select some type of custom object mapping. Every CRM can be configured differently, so your users might want to map objects to some different type of record in their Salesforce or different fields in their Salesforce.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
And typically that's what developers would have to build on their own, is this UI for your users to configure these different settings for every single integration. That's also going to be what's provided by the Paragon SDK.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
It's not just that initial onboarding and authentication experience, but also the configuration end user UX for different settings like custom field mapping, selecting which types of features on your integration that your user might want to configure, And that's also going to be provided fully out of the box by Paragon SDK. With integrations, different APIs might have different rate limits.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
They might have different policies that you have to conform with. And your developers typically have to learn these different nuances for every API and write code individually to conform to those different nuances.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
With Paragon, because we build and maintain the connector with each of the integrations that we support in our catalog, we're automatically going to handle for things like retries, things like rate limits.
The Changelog: Software Development, Open Source
Open source threaded team chat?! (Interview)
And so we look at this as sort of the backend or infrastructure layer of the integration problem that we have spent the last five years essentially building and optimizing the Paragon infrastructure to act as the integration infrastructure for your application.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
Yeah, so there's a lot here, and I think there's a lot of aspects to the different problems that you have to solve in the integration story in building these integrations and also providing them in a user-friendly way for your customers to self-serve and onboard and consume those integrations. So part of what the Paragon SDK provides is that embedded user experience.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
Again, what we call our Connect Portal. That's going to provide the authentication for your users to connect their accounts. That's going to be the initial onboarding. But in addition to that, your users may also want to configure different options or settings for their integrations.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
A common example that we see for Salesforce or for CRM integrations in general is that your users may want to select some type of custom object mapping. Every CRM can be configured differently, so your users might want to map objects to some different type of record in their Salesforce or different fields in their Salesforce.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
And typically, that's what developers would have to build on their own, is this UI for your users to configure these different settings for every single integration.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
That's also going to be what's provided by the Paragon SDK is not just that initial onboarding and authentication experience, but also the configuration end user UX for different settings like custom field mapping, selecting which types of features on your integration that your user might want to configure. And that's also going to be provided fully out of the box by Paragon SDK.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
With integrations, different APIs might have different rate limits. They might have different policies that you have to conform with. And your developers typically have to learn these different nuances for every API and write code individually to conform to those different nuances.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
With Paragon, because we build and maintain the connector with each of the integrations that we support in our catalog, we're automatically going to handle for things like retries, things like rate limits.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
For example, Paragon knows the rate limit for each provider and will automatically throttle your requests so that you can conform to the rate limit for those providers and be able to intelligently retry requests in the event that you exceed the rate limit or a request fails.
The Changelog: Software Development, Open Source
#define: piggyback (Friends)
And so we look at this as sort of the backend or infrastructure layer of the integration problem that we have spent the last five years essentially building and optimizing the Paragon infrastructure to act as the integration infrastructure for your application.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
Yeah, so there's a lot here, and I think there's a lot of aspects to the different problems that you have to solve in the integration story in building these integrations and also providing them in a user-friendly way for your customers to self-serve and onboard and consume those integrations.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
So part of what the Paragon SDK provides is that embedded user experience, again, what we call our Connect Portal. That's going to provide the authentication for your users to connect their accounts. That's going to be the initial onboarding. But in addition to that, your users may also want to configure different options or settings for their integrations.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
A common example that we see for Salesforce or for CRM integrations in general is that your users may want to select some type of custom object mapping. Every CRM can be configured differently, so your users might want to map objects to some different type of record in their Salesforce or different fields in their Salesforce.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
And typically, that's what developers would have to build on their own, is this UI for your users to configure these different settings for every single integration.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
That's also going to be what's provided by the Paragon SDK is not just that initial onboarding and authentication experience, but also the configuration end user UX for different settings like custom field mapping, selecting which types of features on your integration that your user might want to configure. And that's also going to be provided fully out of the box by Paragon SDK.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
With integrations, different APIs might have different rate limits. They might have different policies that you have to conform with. And your developers typically have to learn these different nuances for every API and write code individually to conform to those different nuances.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
With Paragon, because we build and maintain the connector with each of the integrations that we support in our catalog, we're automatically going to handle for things like retries, things like rate limits.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
For example, Paragon knows the rate limit for each provider and will automatically throttle your requests so that you can conform to the rate limit for those providers and be able to intelligently retry requests in the event that you exceed the rate limit or a request fails.
The Changelog: Software Development, Open Source
Reverse rug pull, so cool? (Friends)
And so we look at this as sort of the backend or infrastructure layer of the integration problem that we have spent the last five years essentially building and optimizing the Paragon infrastructure to act as the integration infrastructure for your application.