Most of your data is already in Snowflake, and Refyner reads it there. For the rest – the SharePoint file finance owns, the Google Sheet the marketing team maintains, the Postgres database behind the app – connectors land it in your warehouse on a schedule, so it can be joined, cleaned and modelled with everything else.
Anything already landing in Snowflake through Fivetran, Airbyte, Snowpipe or a native connector is read directly – there is nothing to reconnect. Connectors are for the sources that are not there yet.
Every dataflow writes to your own Snowflake. That is the only place output lands – Refyner does not copy results anywhere else. For the two BI tools most teams run, Refyner can additionally trigger a refresh once a run completes, so dashboards pick up the new data without waiting for their own schedule.
Power BI and Tableau are refresh triggers, not outputs: the data itself stays in Snowflake and those tools read it from there. Because the result is an ordinary warehouse table, any other tool that connects to Snowflake can read it with no connector at all.
Authenticate, pick the file, table or query, and choose where it lands in your Snowflake. Credentials are stored encrypted; the target schema is yours.
Data arrives as a table in your own Snowflake account, and the warehouse stays the system of record. Where a source has no staging area of its own, data may be staged temporarily in the Refyner environment for the duration of the load and is deleted once it completes.
Join the extract to your existing data, clean and aggregate it, and put the whole dataflow on a schedule. The extract refreshes as part of the same run.
Every tool in this category has connectors, and a long list of logos tells you very little. If you need hundreds of SaaS APIs with managed schema drift, a dedicated ingestion tool does that better, and Refyner reads whatever it lands in Snowflake. What Refyner adds is what happens next: the joins, cleans, aggregations and scheduled refreshes that turn a landed table into something the business uses – built by the analyst, in one tool.
In your own Snowflake account, as tables you own, and transformation runs there as pushdown SQL. During ingestion, where a source has no staging area of its own, data may be staged temporarily in the Refyner environment and is deleted once the load completes – see the security model.
No. They are included in Refyner Cloud from $99/month for five users. Runs are charged at $3 per compute hour – source ingestion, dataflow runs and schedules – see pricing.
On whatever schedule you set, as part of the dataflow that uses it. There is no separate orchestration tool and no refresh cap by plan tier.
Yes. Tell us what you need and we will say whether it is on the roadmap and when. If it already lands in Snowflake another way, Refyner reads it today.
Connect a source, join it to what you already have in Snowflake, and put the dataflow on a schedule.
Refyner