Bubble → Zapier: Dev fields end with data types like “Text” but Live fields don’t — causes Zapier mapping errors

Need help Plugins
1

Hi everyone,
I’m running into a weird issue when integrating Bubble with Zapier, and I can’t find any official explanation for it.

:wrench: Setup

  • I have a workflow trigger in Bubble using the Zapier plugin (type: us_registered_log).

  • My database field is named fbclid (confirmed — same in both dev and live databases).

  • The Zapier trigger sends this data to a Facebook Conversion API step via Click ID (fbc).

:test_tube: What happens

  • In version-test (dev), Zapier shows the field as Fbclid Text.

  • In live, Zapier shows the field as Fbclid.

  • The trigger runs fine in both environments individually, but when I use one Zap for both, the mapping breaks because Zapier treats these as different field names.

:brain: What I’ve tried

  • Verified the database schema (field name = fbclid in both environments).

  • Reconnected the Bubble account and refreshed fields.

  • Deployed all changes to Live.

:red_question_mark:Question

Is this suffix (Text, Boolean, etc.) automatically added in development by design?
If so:

  • Is there a way to make dev and live use the same field labels?

  • Or can I disable the “Text” suffix in the dev environment’s Zapier connector?

Would love to hear from anyone who’s encountered this before.