Quick overview Youtube Video: https://youtu.be/QyIalCCy6s8?si=Zlmde_oZz3qbDGwJ Github Repo: https://github.com/blankarrayy/automated-gym-checkin-system This workflow handles gym entry via QR codes by validating check-in requests against Supabase subscription data, logging entry attempts in Supabase, it also generates QR codes for check-in and registration and syncs new user IDs to Google Sheets. How it works Receives a POST request on the /gymcheckin webhook with header authentication and an entry_id query parameter. Looks up the entry_id in the Supabase entry_logs table to detect whether the QR code was already used. If the entry_id is unused, extracts the user ID from the request body and fetches subscription records from the Supabase gym_sub table. Validates that the user exists and has an active subscription, then writes an entry attempt record to the Supabase entry_logs table. Returns a webhook response granting entry (200), rejecting unknown users (401), rejecting inactive subscriptions (401), or rejecting reused QR codes (409).
Tags
SupabaseRelated workflows
See all Supabase→Better Oauth2.0 workflow for Pipedrive CRM with Supabase
This workflow provides an OAuth 2.0 auth token refresh process for better control. Developers can utilize it as an alternative to n8n's built-in OAuth flow to achieve improved control and visibility. In this template, I've used Pipedrive API, but users can apply it with any app that requires the authorization_code for token access. This resolves the issue of manually refreshing the OAuth 2.0 token when it expires, or when n8n's native OAuth stops working. What you need to replicate this Your database with a pre-existing table for storing authentication tokens and associated information. I'm using Supabase in this example, but you can also employ a self-hosted MySQL. Here's a quick video on setting up the Supabase table. Create a client app for your chosen application that you want to access via the API. After duplicating the template: a. Add credentials to your database and connect the DB nodes in all 3 workflows. Enable/Publish the first workflow, "1. Generate and Save Pipedrive tokens to Database." Open your client app and follow the Pipedrive instructions to authenticate. Click on Install and test. This will save your initial refresh token and access token to the database. Pleas
Match product manager jobs with Supabase, Anthropic Claude, Adzuna, and Resend
Quick overview This workflow ingests job postings from Greenhouse/Lever/Ashby job boards, Adzuna, and RemoteOK into a Supabase jobs pool, then daily uses Anthropic Claude to score a short list against a single candidate profile and emails the best matches via Resend. How it works Runs every 3 hours to fetch job listings from curated Greenhouse, Lever, and Ashby ATS boards, Adzuna searches, and the RemoteOK API. Parses each source into a common job format (title, company, location, URL, description, and posted date). Deduplicates jobs, drops postings older than 90 days, marks “fresh” jobs, and upserts the results into a Supabase jobs table. Runs daily at 08:00, loads the single role profile and pulls up to 15 fresh jobs from Supabase that roughly match the role keyword. Removes jobs already matched for that role using the Supabase user_job_matches table, then batches the remaining jobs and sends them to Anthropic Claude for fit scoring. Keeps jobs at or above the configured minimum score, saves the new matches back to Supabase, and sends an HTML email digest to the role’s email address via Resend. If any execution fails, an error workflow formats the failure details and sends an ale
Send DocuSign envelopes with Supabase contract data
Quick overview This workflow is triggered by another n8n workflow, fetches an assessment record from Supabase, generates an HTML contract, and sends it as a DocuSign envelope using JWT authentication in either production or sandbox based on the recipient email, then writes the envelope ID and status back to Supabase. How it works Receives an execution request from another workflow with an assessment ID (and optional contract title). Retrieves the matching assessment record from the Supabase assessments table. Generates a styled contract HTML document from the assessment data and Base64-encodes it for DocuSign. Chooses the DocuSign sandbox or production path based on whether the contact email contains a specific marker string. Calls a Supabase Edge Function to create a DocuSign JWT assertion, exchanges it for a DocuSign access token, and creates a “sent” envelope with two signers and anchor-based signature tabs. Updates the Supabase assessment record with the DocuSign envelopeId and sets the contract status to envelope_sent. Setup Create and connect Supabase credentials in n8n, and update the Supabase project URL for the Edge Function endpoint (/functions/v1/docusign-sign-jwt). Conf