2

I wonder how Saas companies like Zapier, Zendesk, etc...build a lot of common 3rd party integrations that perform the same set of tasks. I mean, do they just brute force in building those market place integrations or do they have an architecture where everything just works if the API keys are configured?

Eg: github, gitlab, Jira apis kind of do the same set of tasks but their APIs are different in structure. Is there a normalisation technique behind the scenes or they just build the same stuff 3 times.

Comments
  • 0
    Actually mostly the company or people hired by the company make the integrations atleast on zapier. Though it is possible that nobody releated to the company made it since they dont verify that.
  • 1
    If the architecture is any good, there is a business logic layer that has nothing to do with how the API is structured, and a set of wrappers for each service.
  • 0
    SaaS companies like Zapier and Zendesk often use a normalization layer or internal abstraction architecture. This lets them build a unified interface internally, mapping different APIs (like GitHub, GitLab, Jira) to common tasks. While some custom coding is still needed, this reduces the need to rebuild logic repeatedly. I'm more interested in how their marketing is built inside the company, since the competition is very high, and you need large agencies like https://aimers.io/ to manage it.
Add Comment