If you're sending form data from Webflow into the CMS via Zapier and see an error about the required slug field, it means Webflow expects a unique "slug" for the CMS item, but you're not passing one. Here’s how to fix it:
1. Understand the Slug Requirement
- A slug is a URL-friendly version of a CMS item's title, often used to construct the item’s page URL.
- Webflow requires this for all CMS items, whether you're creating them manually or via integrations like Zapier.
2. Create a Slug in Your Zap
- In your Zap (usually a "Create Item in Webflow CMS" action), add a field that maps to the "Slug".
- Use a unique and URL-safe string (e.g., use form fields like a combination of name and timestamp).
Example combinations:
- {{Name}}-{{Zap Meta Timestamp}}
- {{Email}}-{{Zap Meta ID}}
Just remove spaces and special characters using Zapier Formatter if needed.
If the form fields may contain spaces or special characters:
- Add a "Formatter" step before the Webflow action.
- Use Text → Replace to:
- Replace space characters with hyphens.
- Optionally, remove or replace special characters like @, !, &, etc.
- Then feed this cleaned version into the Slug field in the Webflow CMS step.
4. Confirm Slug Uniqueness
- Webflow requires slugs to be unique within a CMS collection.
- Adding a timestamp or a Zapier unique ID (like Zap Meta ID) ensures uniqueness.
5. Test Your Zap
- After setting up the slug, run a test submission to ensure successful item creation.
- If it fails, double-check that:
- The slug is passed and not blank.
- It contains valid URL characters (alphanumeric and hyphens are safe).
Summary
To resolve the required slug field issue in a Webflow-Zapier integration, include a unique, URL-safe string in the "Slug" field of the Zap's CMS action—ideally by combining form data with a timestamp or unique ID. Use Zapier Formatter if needed to clean the slug input.