SUPABASE n8n INTEGRATION: AUTOMATE SUPABASE WITH N8N

The "Get a row" action retrieves a specific single row from any table in your Supabase database. This is your go-to action when you need to fetch one precise record based on specific conditions—perfect for looking up user details, checking order status, or validating data before processing.

Key parameters: Credential to connect with (required), Use Custom Schema (optional), Table Name or ID (required), and Select Conditions (optional filters to identify the row).

Typical use cases: Fetch user profile data when a webhook receives a user ID, look up product details before creating an invoice, retrieve configuration settings stored in a settings table, and validate that a record exists before attempting an update.

Use this action when you expect exactly one result. If multiple rows could match your conditions, use "Get many rows" instead and limit to 1.

The "Get many rows" action pulls multiple records from your Supabase table, with powerful filtering and pagination options. It's ideal for batch operations, generating reports, syncing data sets, or feeding lists into subsequent workflow steps.

Key parameters: Credential to connect with (required), Table Name or ID (required), Return All toggle, Limit (default: 50), Filter options, Must Match (AND/OR logic), and Filters section for condition building.

Typical use cases: Export all orders from the last 24 hours to a Google Sheet, fetch all active users for a weekly email digest, retrieve unprocessed leads to push into your HubSpot CRM, and pull inventory items below threshold for restock alerts.

💡 Pro tip: Combine with n8n's "Split In Batches" node when processing large datasets to avoid memory issues and rate limits on downstream services.

The "Delete a row" action permanently removes records from your Supabase table based on conditions you specify. Use it for data cleanup, handling unsubscribe requests, removing expired entries, or maintaining data hygiene in automated workflows.

Key parameters: Credential to connect with (required), Use Custom Schema (optional), Table Name or ID (required), Select Type (manual or expression), Must Match (AND/OR logic), and Select Conditions to identify target rows.

Typical use cases: Remove user data when they request account deletion (GDPR compliance), clean up temporary or expired session records, delete cancelled orders after a grace period, and remove duplicate entries detected by a deduplication workflow.

⚠️ Warning: Deletion is permanent. Always test your conditions with a "Get a row" action first to confirm you're targeting the correct records. Consider soft-deletes (updating a deleted_at column) for critical data.

The "Create a row" action inserts a new record into your Supabase table. This is fundamental for any workflow that needs to store data—capturing form submissions, logging events, creating user records, or syncing data from external sources.

Key parameters: Credential to connect with (required), Use Custom Schema (optional), Table Name or ID (required), Data to Send (auto-map or manual definition), and Fields to Send for defining column values.

Typical use cases: Store new contact form submissions from your website, create user records when someone signs up via Auth0 or Clerk, log automation events for debugging and audit trails, and import leads from LinkedIn or other lead generation tools.

💡 TIP: Use the "Auto-Map Input Data" option when your incoming data field names already match your Supabase column names—it saves significant configuration time.

The "Update a row" action modifies existing records in your Supabase table. It's essential for keeping data current—updating statuses, syncing changes from external systems, incrementing counters, or correcting information based on new inputs.

Key parameters: Credential to connect with (required), Use Custom Schema (optional), Table Name or ID (required), Select Type (manual or expression), Must Match (AND/OR logic), Select Conditions to identify target rows, Data to Send (auto-map or manual), and Fields to Send for defining new values.

Typical use cases: Update order status when payment is confirmed via Stripe webhook, sync contact information changes from your CRM back to Supabase, mark tasks as complete when checked off in a project management tool like ClickUp, and update user subscription tier after a successful upgrade.

Best practice: Always include a unique identifier in your Select Conditions to avoid accidentally updating multiple rows. Test with "Get a row" first using the same conditions to verify you're targeting the right record.