[jlund-molfese]

I wish API integrations never took that long! But it's dependent on who you're integrating with and what your product looks like. I'm the engineering manager of the payroll integrations team at a company that does workplace savings plans.

Sometimes even when you're making calls to dozens of different endpoints they're easy, but other times, you end up guessing at how to access undocumented functionality within a GraphQL API that has introspection turned off, or working around entity modeling that's completely different from your system and requires a lot of translation. Or you work with an API whose indexes variably start from 1, 0, -1, and -2 in different endpoints. These generally aren't hard technical challenges to solve, and something like Devin that could take care of most surface-level problems you see while integrating with some XML API from 2007 would be welcome.

There are companies like https://www.tryfinch.com and https://www.merge.dev that try to solve these issues, but their abstractions also reduce flexibility and aren't a perfect for all HRIS integration use cases right now.

[rguldener]

I agree. Integrations can be incredibly cumbersome if you have to learn each API from scratch.

There are also more flexible solutions like https://www.nango.dev

It handles the API-specific complexities (auth, retries, webhooks, per-customer config, pre-built templates) but allows you to implement the exact use case + data model you need.

It's open source/source available.

(disclaimer: I am a founder)

[babyent]

Hey that’s really cool. I read the FAQ on connection.

So if there are 10 users, the free tier lets me give them the ability to add up to 3 integrations? Is it 3 per user?

Thanks

[neom]

Been using https://www.laminar.run/ here and there and found it a good mix of abstract and being able to get in there.