rguldener
Joined 16 years ago
Karma
631
Submissions
130
Member since
Oct 17
Founder @ nango.dev
View on Hacker NewsRecent submissions
Comment · 7 months ago
Author here, the build happens together with building your app.
Once built, the code executes deterministically at runtime.
The news here is the AI reading the API docs, assembling requests, and iterating on them until it works as expected.
This sounds simple, but is time consuming and error prone for humans to do.
Comment · 11 months ago
Nango | Staff backend engineer | Remote | Full time | $120-200k + equity
Nango (YC W23) is an open-source developer infrastructure for product integrations.
We power the integrations of Replit, Semgrep, Motion, Vapi, Exa, and hundreds of other AI companies.
Small but highly experienced team, hard technical challenges (scale + infra devtool running untrusted user code), tons of ownership, direct customer contact, growing very fast.
We are looking for a Staff engineer who can touch every part of the stack and is passionate about dev infrastructure.
Website: https://nango.dev Jobs: https://nango.dev/careers
Comment · 11 months ago
Nango is an open-source alternative: https://nango.dev
Especially if you use pipedream for integrations in your agent or product.
(I’m one of the founders)
Comment · 1 year ago
Nango | Staff backend engineer | Remote | Full time | $120-200k + equity
Nango (YC W23) is an open source product: Developer infrastructure for product integrations.
We power the integrations of Semgrep, Motion, Vapi, Exa, and hundreds of other B2B software.
Small but highly experienced team, hard technical challenges (scale + infra devtool running untrusted user code), tons of ownership, direct customer contact, growing very fast.
We are looking for a Staff engineer that can touch every part of stack and is passionate about dev infrastructure.
Website: https://nango.dev Jobs: https://nango.dev/careers
Comment · 1 year ago
It varies a lot. Which is why we always recommend to start with the feature requirements/user problem and work backwards from there.
Examples: - Low latency to show X last emails a person had with a specific email address
- Enriching data from the emails/calendar with other data from your product (E.g. mapping email recipients to contacts)
- Knowing when a calendar event has changed (sometimes also possible with webhooks)
- Detecting deletes (maybe also possible with webhooks, not sure for gmail/calendar)
Comment · 1 year ago
Founder of https://www.nango.dev here.
A lot of teams use us for their Gmail & Google calendar integrations.
If you want to run complex queries across large parts of the data, syncing + indexing on your side will be necessary. Limits on filters, pagination & rate limits make it infeasible to search across most of a user's inbox without tens of seconds to minutes of latency.
But before you sync all the data, I would test if your users actually need to run such queries.
Both Gmail & Google Calendar have a query endpoint that searches across many fields. I would start with a simple tool for your agent to run queries on that, and expand from there if necessary.
Both Nango and Composio could do this for you.
With Nango, you would also get syncs on the same platform, if it turns out you need them.
Hope this helps!
Comment · 1 year ago
Thanks for the flag, should be fixed!
Comment · 1 year ago
Nango | Staff backend engineer | Remote | Full time | $120-200k + equity
Nango (YC W23) is an open source product: Developer infrastructure for product integrations. We power the integrations of Semgrep, Motion, Vapi, Exa, and hundreds of other B2B software.
Small but highly experienced team, hard technical challenges (scale + infra devtool running untrusted user code), tons of ownership, direct customer contact, growing very fast.
We are looking for a Staff engineer that can touch every part of stack and is passionate about dev infrastructure.
Website: https://nango.dev Jobs: https://nango.dev/careers