# Create entity type A when entity type B is created **URL:** \ **Category:** Get Help\ **Created:** [June 24, 2025, 6:22am UTC](https://community.fibery.io/t/create-entity-type-a-when-entity-type-b-is-created/9039 "2025-06-24T06:22:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [June 24, 2025, 6:22am UTC](https://community.fibery.io/t/create-entity-type-a-when-entity-type-b-is-created/9039/1 "2025-06-24T06:22:56Z")
I need to be able to use a create trigger to create another entity. Example: when a Meeting entity is created, for each attached user create an Invite entity, which they are notified of. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [June 24, 2025, 8:12am UTC](https://community.fibery.io/t/create-entity-type-a-when-entity-type-b-is-created/9039/2 "2025-06-24T08:12:07Z")
If a Meeting is linked to a set of Users (e.g. via an `Attendees` field) then that implies that each User is linked to the Meeting (via a `Meetings attended` field or whatever). Instead of using the creation of the Meeting as the trigger, why not use an automation in the User database, triggered by the linking of a Meeting to a User. In this way, the automation will be triggered for every User. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 24, 2025, 6:32pm UTC](https://community.fibery.io/t/create-entity-type-a-when-entity-type-b-is-created/9039/3 "2025-06-24T18:32:24Z")
You really have to use @Chr1sG 's suggestion, because when a Meeting entity is _created_ there will not yet be any Users attached to it, so a trigger at creation time will not have anything to process.