> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ordergroove.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ordergroove.com/_mcp/server.

# Using Prebuilt Connectors

Building a [custom ETL pipeline](/docs/data/custom-pipelines) is a great approach for flexibility, but if you prefer a quicker solution, there are prebuilt third-party connectors available for Ordergroove data syncing:

* **Portable**: [Portable.io](https://portable.io/connectors/ordergroove) provides a fully managed no-code Ordergroove connector that can sync data to popular warehouses like Snowflake, BigQuery, and Redshift with minimal setup. This can save significant development time.
* **Fivetran**: [Fivetran](https://www.fivetran.com/connectors/ordergroove) has an Ordergroove connector (currently a "Lite" connector) which automatically extracts Ordergroove data and loads it into your destination. It handles the API calls and schema for you, and provides a managed service for ongoing syncs.
* **Saras (Daton)**: [Saras Analytics](https://www.sarasanalytics.com/daton/ordergroove) offers Daton, an ELT platform with an Ordergroove integration. It allows you to configure Ordergroove as a source and pull data on a schedule into your data warehouse without coding.
* Other ETL tools and integration platforms may also support Ordergroove or can be configured with REST API modules.

If you choose to use a prebuilt connector, ensure it aligns with the best practices outlined — for example, check that it respects incremental updates and doesn't overload the API. You may still need to handle custom logic like webhooks for Order and Item deletions. But for most use cases, these tools can significantly speed up the implementation.