How can I fix the required slug field issue when integrating Webflow with Zapier for sending form data into CMS?
TL;DR
- Map a dynamic form field (like name or title) to the slug in Zapier and format it using Zapier’s Formatter to remove special characters, replace spaces with hyphens, and convert to lowercase.
- Add a fallback (e.g., timestamp) to prevent duplicates, then test the Zap to ensure the CMS item is created with a valid slug.
The "required slug field" error happens when trying to send form data from Webflow to a CMS Collection via Zapier, but the CMS expects a slug and none is provided.
1. Understand the Slug Requirement
- Every CMS item in Webflow must have a unique slug (the URL-friendly identifier).
- When creating a new item via Zapier, Webflow requires the slug—either auto-generated using a field (like title) or passed explicitly.
2. Set Up Auto-Slugging in Zapier
- In the Zapier "Create Live Item" or "Create Item" action for Webflow:
- Ensure the slug field is mapped to a value.
- You can use a dynamic field from the form—like the name or title—but convert it to a slug-safe string.
3. Proper Slug Formatting
- A slug must:
- Only contain lowercase letters, numbers, and hyphens.
- No spaces, punctuation, or capitals.
- Use Zapier’s Formatter > Text > Replace/Lowercase steps before the Webflow action to sanitize the field:
- Replace spaces with hyphens.
- Remove special characters.
- Convert to lowercase.
4. Add a Fallback Slug (Optional)
- If the form input could be empty or produce duplicate slugs, append a timestamp or random ID:
- e.g.,
"{{Name}}-{{zap_meta_timestamp}}", which might becomejohn-doe-172347823.
5. Save Changes and Retest Zap
- After adjusting your Zap:
- Retest the step.
- Check in Webflow CMS that the item was created and the slug field is populated properly.
Summary
To fix the required slug field issue in Zapier-Webflow CMS integration, ensure the slug is dynamically mapped and correctly formatted in your Zap, using Zapier's Formatter tools if needed. Always test to confirm successful CMS item creation.