Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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!



Thank you that is really helpful. Will check Nango out.

When teams integrate Gmail or other tools with Nango, what usually triggers them to start syncing data instead of just using the query endpoints? Is there a specific type of query or user behavior that makes them realize they need to index and sync data? Just curious


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)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: