Uniqueness constraints for Entities?

Is there a way to create uniqueness constraints for an Entity? For instance, I would like a Contacts DB where each contact’s email is unique/primary key, so that an automation that tries to create a new contact with an email that already exists should fail.

Or is there some trick i can use to get this effect?

1 Like

Fibery does not currently have validation rules (e.g. uniqueness, required fields, range-checking etc.)
You can implement automations that flag up violations, but there is no enforcement mechanism.

2 Likes

Is there a feature request for this? I feel like I saw one but can’t find it now.

Having a unique/primary key constraint for new entities is high up on my feature wishlist.

3 Likes
1 Like