Question for Supabase (PostgreSQL) and Webflow CMS

Design help Data API
1

Hi Webflow Community!

I’m building an automated brand management system that syncs data between Supabase (PostgreSQL) and Webflow CMS using API v2. I’ve hit some roadblocks with UPDATE and DELETE operations and would love your insights.

:wrench: Current Setup

  • PostgreSQL with pg_net extension

  • Webflow API v2 for CMS operations

  • Automated brand data synchronization

:prohibited: Issues I’m Facing

1. DELETE Operations = 401 Unauthorized


// This fails with 401 error

DELETE /v2/collections/{collection_id}/items

Authorization: Bearer [my_token]

CREATE and READ work fine, but DELETE always returns “Request not authorized”

2. PATCH Operations - PostgreSQL Limitation

PostgreSQL’s net extension doesn’t have net.http_patch() function:

  • :white_check_mark: net.http_post() - available

  • :white_check_mark: net.http_get() - available

  • :cross_mark: net.http_patch() - doesn’t exist

Using POST instead of PATCH creates new items rather than updating existing ones.

3. Live vs Draft Updates

Discovered that live update endpoints only work for published items, but most of my items are drafts.

:light_bulb: Questions for the Community

  1. API Token Permissions: Do I need special permissions for DELETE operations? How do I enable them?

  2. PostgreSQL PATCH Workaround: Has anyone successfully implemented PATCH operations from PostgreSQL? What approach did you use?

  3. Alternative Solutions:

  • Should I use Supabase Edge Functions instead of direct PostgreSQL?

  • Is N8N a better choice for Webflow API automation?

  • Any other recommended tools for automated Webflow CMS management?

  1. Best Practices: What’s the recommended workflow for automated CRUD operations with Webflow API?

:white_check_mark: What’s Working

  • CREATE operations (POST) - perfect

  • READ operations (GET) - perfect

  • Webflow MCP tools - can delete successfully

:hammer_and_wrench: My Goal

Build a system where:


-- This should work for both CREATE and UPDATE

SELECT sync_brand_smart('Brand Name'); -- Returns: SUCCESS

Has anyone solved similar integration challenges? I’d really appreciate your experience and suggestions!

Thanks in advance! :folded_hands:

Here is my site Read-Only: LINK
(how to share your site Read-Only link)

2

Hi there!

For DELETE operations through the API, you’ll need to ensure your API token has “read and write” permissions. Here’s how to set this up:

  1. Go to Site settings > Apps & integrations > API access
  2. Generate a new token and select “read and write” access
  3. Store your new token securely

Please note that API tokens automatically expire after 365 days of inactivity.

For questions about PostgreSQL, Supabase, and N8N integrations, you can find helpful information in our documentation:

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.

3

Hi @ShawnShen - welcome to the community :waving_hand:

For issue #1, as long as your token has read/write abilities for CMS scopes, you shouldn’t need any other special permissions for the Delete route. It looks like the endpoint you’re trying to call is the Delete Items API where you can delete multiple items at a time. I’d double check to make sure you’re sending in the items: [ ... ] array in your request.

For your 2nd topic re: PATCH operations, this may be a PostgreSQL-specific concern rather than Webflow and I’m less familiar with those extensions, but let me know if you’re referring to a Webflow SDK operation instead.

For #3, you’re correct that the /live API endpoints only work for published items. To work with unpublished (or “staged”) items, which include your draft status items, I would use the APIs specified in our docs under CMS → Collection Items → Staged Items.

On alternative solutions - many Webflow devs have their own homegrown solutions managing site content (like you are doing right now), whether it’s creating serverless functions for specific automations, or full-scale internal admin apps to manage content. But many devs also have automations in places like Make, Zapier, N8N as well, so I think if you’re running into issues with your PostgreSQL solution, those may be perfectly acceptable solutions to consider too :slight_smile:

1 Like