· Owner at No Black Swan

Issue: Webflow API Call Works in Postman but Not in Xano Trigger

I am trying to automate Webflow CMS updates using a trigger in Xano that runs when a new row is inserted into my database.

  1. I tested the Webflow API call in Postman, and it works perfectly (202 Accepted).

  2. I imported the exact same cURL request into Xano's trigger, but it fails.

  3. The error message from Webflow varies, sometimes stating Missing param: action, other times giving no clear indication.


What I Did:

  1. Built a working API request in Postman:

    • Uses application/x-www-form-urlencoded in Postman.

    • Returns 202 Accepted in Webflow CMS.

  2. Converted the request to JSON for Xano:

    • Matched the structure that worked in Postman.

    • Used this.name, this.slug, etc., in the trigger function.

  3. Checked Webflow CMS schema:

    • Confirmed the correct field names.

    • Ensured Rich Text (rich-text) uses HTML formatting.


The Problem:

  • The trigger runs successfully in Xano but Webflow rejects the request.

  • I suspect that Xano handles triggers differently from regular API calls, and I may need to adjust how data is referenced inside the trigger.

  • Should I be using this.field_name instead of $input.field_name in Xano?


What I Need Help With:

  1. How should I structure the API request inside a Xano trigger?

  2. Is there a different way to reference the row being inserted (this vs. $input)?

  3. Are there known differences in how Xano sends data from a trigger vs. an API endpoint?

💡 Any guidance or example setups would be greatly appreciated! I can provide more screenshots if needed - below are for Postman I am using which gives 202 and I replicated to Xano API Call and the Trigger. and two screenshots from the params in the trigger.

The only difference I can see between the API and the trigger is the "inputs" which I don't see in the Trigger.

Sorry Noob Yeah?!?

Thanks in advance! 🚀


2 replies