Send Emails (using the Codemagic email functionality) to dynamically determined email-adresses.

[erbenjak]

Use case

Use Cases could include:
1. If one wishes to send an email to the employee which created i.e. a pull request, that then in turn triggered the build. This email-adress is only known by the time the workflow is executed.

2. If some company policy exists by which certain members of a team must be informed about new releases and futhermore the exact members dependend on something dynamic i.e. the state of the project or criticallity of the new build. Again these email-adresses are then only known at runtime.

...

Idea

Currently one can still send these emails, by using a third party provider like SendGrid or Mailgun in a custom publish step. 

Since there are however multiple use cases, where users might need to send emails to dynamically determined addresses, it seems that a more streamlined solution within Codemagic would be highly valuable. This not only increases workflow simplicity and readability, but also eliminates the need for every user to create their own "workaround".

I image a solution would then work something like this:

1st - During the build proces an email-adress is dynamically determined:

- name: Setting dynamic email address
        script: |
          export email_address = #some_api_call

2nd - the variable storing this address is then used during publishing

publishing:
     email:
       recipients:
         - $email_address

This is currently not possible, which was confirmed by support staff in this thread: https://github.com/orgs/codemagic-ci-cd/discussions/2198

[Ycoi]

Thanks for the idea @erbenjak! I’ll mark this down. I think this is a good addition and good use case to have in mind when otherwise improving the email notifications and adding options for passing data between different build stages.

[jkoenig134]

Additionally it would be great to have a new CM_ variable containing the commiter email, so that we don't have to extract this ourselves.

[jkoenig134]

@mikhail-tokarev could you elaborate what we can do now?