# Create entity via email

**URL:** <https://community.fibery.io/t/create-entity-via-email/4236>\
**Category:** Get Help\
**Created:** [April 3, 2023, 2:42pm UTC](https://community.fibery.io/t/create-entity-via-email/4236 "2023-04-03T14:42:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\
**Post date:** [April 3, 2023, 2:42pm UTC](https://community.fibery.io/t/create-entity-via-email/4236/1 "2023-04-03T14:42:30Z")

</div>

Hi,

Does anyone have a solution or workaround to ‘create an entity by sending an e-mail to a special email address’?

ClickUp and Trello have a unique email address per list or board. If you send an email to that email address, it creates an entity.

Would be great if I can somehow manage the same in Fibery via Zapier/Make/N8N/something else 😄

Else I will make a feature request for this.

Yvette

---

<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:** [April 3, 2023, 3:24pm UTC](https://community.fibery.io/t/create-entity-via-email/4236/2 "2023-04-03T15:24:03Z")

</div>

You could set up an email integration tied to a generic email address, e.g. [fibery@mybusiness.com](mailto:fibery@mybusiness.com)  
Then, you can set up a variety of automations that will create an entity whose type and name depend on (parts of) the subject of any incoming message.  
So, for example, an email with the subject ‘Task - Do this’ would create a Task entity called ‘Do this’ and so on.

Alternatively, you could set up multiple email addresses e.g. [task@mybusiness.com](mailto:task@mybusiness.com), [project@mybusiness.com](mailto:project@mybusiness.com), etc. and set up integrations for each of them.  
This would make it easier for users to send emails (not having to worry about formatting etc. - just take the subject as the name) but is a bit more work to set up.

---

<div class="post-metadata">

**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\
**Post date:** [April 3, 2023, 4:57pm UTC](https://community.fibery.io/t/create-entity-via-email/4236/3 "2023-04-03T16:57:01Z")

</div>

Oh boy, I didn’t even thought about Fibery’s built-in integration 😅 And didn’t searched in the guide. Apologies; this is awesome 😄

---

<div class="post-metadata">

**Author:** ![gok](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gok/32/6090_2.png) [@gok](https://community.fibery.io/u/gok)\
**Post date:** [April 22, 2023, 11:09am UTC](https://community.fibery.io/t/create-entity-via-email/4236/4 "2023-04-22T11:09:25Z")

</div>

Anyone have an example of this done?

---

<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:** [April 22, 2023, 11:52am UTC](https://community.fibery.io/t/create-entity-via-email/4236/5 "2023-04-22T11:52:54Z")

</div>

If you have an active email integration, you will have a Message database, where new emails will appear each time a sync occurs.  
If you link the Message db to another db (e.g. Task) you can create an automation to add a new Task whenever an email Message appears (optionally with filters).  
Ping us in the chat if you have problems getting it working (although you’ll probably only get a response on Monday 🙂)

---

<div class="post-metadata">

**Author:** ![gok](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gok/32/6090_2.png) [@gok](https://community.fibery.io/u/gok)\
**Post date:** [April 23, 2023, 11:07am UTC](https://community.fibery.io/t/create-entity-via-email/4236/6 "2023-04-23T11:07:26Z")

</div>

Ahh, thanks for the clarification. I had somehow missed the email integration topic in the guideline. I’ll set that up first and take it from there. Thanks a lot.
