# Create Entity & Related Entities with button?

**URL:** <https://community.fibery.io/t/create-entity-related-entities-with-button/1182>\
**Category:** Get Help\
**Created:** [November 18, 2020, 7:56pm UTC](https://community.fibery.io/t/create-entity-related-entities-with-button/1182 "2020-11-18T19:56:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [November 18, 2020, 7:56pm UTC](https://community.fibery.io/t/create-entity-related-entities-with-button/1182/1 "2020-11-18T19:56:43Z")

</div>

Hi,

Is it possible right now with buttons to create a new entity along with related entities at once? I’m looking for a way to create a repeatable process. One case I have is an onboarding routine. I’d like to create a “project” entity and, say, a few sub entity “tasks” in one step with a button. If this is not possible, please add a big “+1” from me for this feature, which I imagine may be a part of Templates functionality when they come out.

Thanks!

---

<div class="post-metadata">

**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:** [November 18, 2020, 8:23pm UTC](https://community.fibery.io/t/create-entity-related-entities-with-button/1182/2 "2020-11-18T20:23:29Z")

</div>

Yes, it is definitely possible 🙂

AFAIK you actually do it in 3 stages:

- create the parent entity
- create the child entities
- add the newly-created children to the newly-created parent collection

The API documentation is pretty useful here: [https://api.fibery.io/#create-entity](https://api.fibery.io/#create-entity) & [https://api.fibery.io/#update-entity-collection-field](https://api.fibery.io/#update-entity-collection-field)

You’ll want to know in advance all your type names and the field names for the collections.

---

<div class="post-metadata">

**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:** [August 13, 2021, 12:09pm UTC](https://community.fibery.io/t/create-entity-related-entities-with-button/1182/3 "2021-08-13T12:09:50Z")

</div>

Just thought I’d follow up on this now that automations are up and running.  
No need to use scripting/API any longer, you can trigger an [automation rule](https://community.fibery.io/t/changelog-july-5-automation-rules-currency-exchange-template/1754) to generate child entities when a parent entity is created. Also, fields can be set to default values, and with markdown etc., rich text fields can be populated with template text.

---

<div class="post-metadata">

**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\
**Post date:** [August 13, 2021, 2:59pm UTC](https://community.fibery.io/t/create-entity-related-entities-with-button/1182/4 "2021-08-13T14:59:00Z")

</div>

To add a little context for anyone else, I think it will depend a bit on the use case. More advanced use cases might still need scripting.

The one time I’ve tried something like this, I was trying to add a Vote entity for each member of a Team associated with a Meeting. So, first I have to get the team members associated with the meeting, then loop over the team members and add a Vote entity to the Meeting for each team member and associating each Vote entity with the team member.

---

<div class="post-metadata">

**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:** [August 13, 2021, 5:52pm UTC](https://community.fibery.io/t/create-entity-related-entities-with-button/1182/5 "2021-08-13T17:52:17Z")

</div>

Yeah, you’re right, there are circumstances where it is v. hard (if not impossible) to devise an automation that will create all the entities you need, especially if the logic for their existence is complicated.  
At least some of the use cases have become a little easier 🙂
