You could set up an email integration tied to a generic email address, e.g. email@example.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. firstname.lastname@example.org, email@example.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.
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 )