Connect Everhour to Supabase
Send Everhour tasks, projects, users and 3 more data types to Supabase on a schedule. Refresh as often as every 15 minutes.
Supabase
schema everhour
tasksprojectsuserstime_recordsclients- 1 more data type
How to connect Everhour and Supabase
4 steps. You can preview the Everhour data in Coupler.io before anything reaches Supabase.
Step 1 of 4
Connect Everhour
Enter your Everhour API key. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the Everhour data you want in Supabase.
Step 3 of 4
Connect Supabase
Enter the connection details from your Supabase project's Connect panel, then the schema and table for the Everhour data.
Show 3 more fields Show fewer fields
Step 4 of 4
Choose a write mode and schedule
Every run either replaces or appends the data in Supabase. Run it as often as every 15 minutes.
Each run deletes the existing rows in tasks and loads fresh Everhour data.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your Everhour integrations with these destinations
Get the most of Everhour to Supabase integration
Gather data
Understand data
Automate data
Act on data
6 data types, including Tasks, Projects, Users, Time records and Clients.
With your Everhour API key, entered once when you add the connection.
Yes. On the first successful run, Coupler.io creates the everhour schema and the tasks table if the database user has the privileges to do so, and detects column types from the Everhour data.
Its writes aren't governed by RLS policies, and the tables it creates have RLS turned off. Keep Everhour data in a schema your app doesn't expose through the Data API.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example Clockify or Harvest, and join or append them before the data reaches Supabase.
