How can I fix the issue with Zapier not adding 'https://' to URLs in Webflow collection items when the link field is missing it, causing Webflow to publish it as a subdirectory?

If Zapier sends a URL to a Webflow link field without 'https://', Webflow treats it as a relative path, causing it to publish incorrectly (e.g., as a subdirectory). Here's how to fix it:

1. Add 'https://' in Zapier Before Sending the URL

• In your Zapier Zap, locate the action that sends the data to Webflow (usually the "Create Live Item in Webflow" or "Update Live Item" action).
• Find the field where the external URL is being inserted.
• Use a Formatter Step in Zapier before the Webflow step:
• Set up a Formatter > Text > Replace action.
• Input: the original URL value.
• Replace: ^(?!https?://) (matches strings not starting with http:// or https://).
• With: https:// prepended (though Zapier's Replace tool doesn't support regex groups, so see the workaround below).

2. Use Zapier’s ‘Formatter > Code’ to Add Protocol

• Insert a Webhooks or Code by Zapier step before the Webflow step.

• Choose Code > Run JavaScript.

• Input your URL field as a variable (e.g., inputData.url).

• Use this simple logic:

• If the URL starts with http:// or https://, leave it.

• If not, prepend https://.

• Example Logic (conceptual, without using raw code):

• If URL does not contain '://', then set the output to 'https://' + url. Use this modified URL in the Webflow action.

3. Clean Existing Webflow Entries (Optional)

• Go into your Webflow CMS and manually update any previously submitted link fields missing the https:// prefix.
• Alternatively, set up a Zapier loop to fetch items and update them with corrected URLs.

Summary

To prevent Webflow from treating plain URLs as subdirectories, ensure Zapier always sends URLs prefixed with 'https://'. Use a Code by Zapier step to detect and correct URLs before passing them to Webflow. This guarantees the link field is interpreted correctly.