How can I fix the required slug field issue when integrating Webflow with Zapier for sending form data into CMS?

You're encountering an issue where Webflow requires a slug field when using Zapier to send form data into a CMS collection. This typically happens because the CMS item you're creating via Zapier must have a unique slug, and Webflow doesn't auto-generate it in the Zap.

1. Understand the Role of the Slug

• Slugs are unique URLs for CMS items (e.g., yourwebflowsite.com/blog/my-post-slug).
• When creating new CMS items via Zapier, Webflow requires a slug field, and it won't generate one automatically.

2. Generate a Unique Slug in Zapier

• In your Zapier workflow, use a Formatter step (from Zapier’s built-in tools) to create a slug:
• Choose App: Formatter by Zapier
• Event: Text › Replace
• Set up action: Replace spaces and capital letters in a field like the form’s title or name (e.g., replace spaces with dashes).
• Optionally, use additional data (like a date or random number) to ensure the slug is unique.

3. Map the Slug Field in Webflow Action

• In the Webflow → Create CMS Item action:
• Ensure the slug field is mapped to the output from your Formatter step.
• Example input: "my-form-title" → "my-form-title-2024".

4. Handle Special Characters

• Use Regex or multiple Formatter steps to:
• Lowercase all characters.
• Remove non-alphanumeric characters (e.g., punctuation).
• Replace spaces with hyphens.

5. Test the Zap for Errors

• Run a test in Zapier after setting up the Formatter and slug mapping.
• If Webflow still throws an error, make sure:
• The slug is not empty.
• The slug is unique (check your CMS items for duplicates).
• No invalid characters are being passed.

Summary

To fix the required slug field issue when sending Webflow form data to a CMS via Zapier, you must manually create a unique slug using Zapier's Formatter and map it to the slug field in your Create Item action. This ensures Webflow accepts the new CMS entry without errors.