Answers.Body: <p>I've figured this out (the solution is not in the docs). Follow these steps:</p>
  
  <p><strong>1)</strong> In the amforms plugin's settings, create a custom text field called 'notificationRecipients'.</p>
  
  <p><strong>2)</strong> Add that field to your form's list of fields in the form's settings.</p>
  
  <p><strong>3)</strong> Under the notifications tab of your form, add this to your "Email Recipients" field:</p>
  
  <p><code>defaultAddress@domain.com,{notificationRecipients}</code></p>
  
  <p><strong>4)</strong> Now in your template, add a hidden input in the <code>&lt;form&gt;</code> like so: </p>
  
  <p><code>&lt;input type="hidden" name="fields[notificationRecipients]" value="{{ entry.yourCustomFieldEmailAddress }}"&gt;</code></p>
  
  <p>Keep in mind that multiple emails should be separated by commas like <code>example1@gmail.com,example2@gmail.com,example3@gmail.com</code></p>
  
  <hr>
  
  <p>That's it!</p>
  
  <p>If you don't want the list of email recipients to appear in your notification email, then you need to edit line 24 of craft/plugins/amforms/templates/_display/templates/email.twig to look like this:</p>
  
  <p><code>{% for field in fields if field.getField().handle != 'notificationRecipients' -%}</code></p>
  
  <p>Additional examples and info can be found on these closed issues of the developer's git page:</p>
  
  <ul>
  <li><a href="https://github.com/am-impact/amforms/issues/72" rel="nofollow">#72</a></li>
  <li><a href="https://github.com/am-impact/amforms/issues/86" rel="nofollow">#86</a></li>
  <li><a href="https://github.com/am-impact/amforms/issues/99" rel="nofollow">#99</a></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-18T16:26:53.250Z
Answers.LastActivityDate: 2016-10-18T16:26:53.250Z
Answers.UserDisplayName: Ryan
Body: <p>I have a situation where I need a form to submit and be sent to my company's email address AND to an email address outputted from an email field from the entry that the form sits on. Is it possible to have a hidden input in the template that contains the email addresses I want the notification to go to?</p>
  
Tags: <form><emails><plugin-amforms>
Title: Dynamic email recipients with amforms
ThreadText: # Dynamic email recipients with amforms
  
  (Asked by: username_0 on 2016-10-17)
  
  I have a situation where I need a form to submit and be sent to my company's email address AND to an email address outputted from an email field from the entry that the form sits on. Is it possible to have a hidden input in the template that contains the email addresses I want the notification to go to?
  
  **Tags:** form, emails, plugin-amforms
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-10-18. Score: 2 | Accepted answer
  
  I've figured this out (the solution is not in the docs). Follow these steps:
  
  **1)** In the amforms plugin's settings, create a custom text field called 'notificationRecipients'.
  
  **2)** Add that field to your form's list of fields in the form's settings.
  
  **3)** Under the notifications tab of your form, add this to your "Email Recipients" field:
  
  `defaultAddress@domain.com,{notificationRecipients}`
  
  **4)** Now in your template, add a hidden input in the `<form>` like so:
  
  `<input type="hidden" name="fields[notificationRecipients]" value="{{ entry.yourCustomFieldEmailAddress }}">`
  
  Keep in mind that multiple emails should be separated by commas like `example1@gmail.com,example2@gmail.com,example3@gmail.com`
  
  ---
  
  That's it!
  
  If you don't want the list of email recipients to appear in your notification email, then you need to edit line 24 of craft/plugins/amforms/templates/\_display/templates/email.twig to look like this:
  
  `{% for field in fields if field.getField().handle != 'notificationRecipients' -%}`
  
  Additional examples and info can be found on these closed issues of the developer's git page:
  
  * [#72](https://github.com/am-impact/amforms/issues/72)
  * [#86](https://github.com/am-impact/amforms/issues/86)
  * [#99](https://github.com/am-impact/amforms/issues/99)
  
  
  ---
  
  