Adding an Attachment created by a behavior to an email

[wbtittle]

A client wants a spreadsheet sent to them every week with the status of the project.

I created an Attachment to attach to the email..

I can link to the attachment in the email, but I cannot find the point to ADD the attachment to the email..

The link method works, but you have to be logged in to download the file. Can I set the permissions on a file?

The Behavior Tree
![Screenshot 2023-01-23 at 7 24 40 AM](https://user-images.githubusercontent.com/418631/214087526-d8e9edfa-9a39-492c-9b21-168ff7296550

The Attachment Creation

The eMail Send..

.png)

Where is the magical way to attach the attachment to the email?

[jstanden]

Hi @wbtittle!

We're in the process of replacing behaviors with automations. The main benefit of automations is that you can use scripting and placeholders for any value in all conditions, actions, etc. They also drastically simplify multi-step workflows like interactions. Behaviors by comparison are simpler but much more confined.

What you're looking for is possible in behaviors, but not as intuitive as it should be. If you edit the behavior itself (at the top of your behavior tree in bold), you can add variables to it that are available throughout actions. Add a 'List:Attachments' variable. Set it to the value of the attachment you created. Then the 'Send Email' action will show that variable as an option to include.

In automations, we recommend creating a mail.transactional draft record. You can set every property from there, including file_ids, GPG signing/encrypting, Markdown formatting, custom fields, etc.

A mail.transactional draft will also enter the mail queue so failures are retried, SMTP doesn't block the automation thread, etc. If is_queued@bool: yes then it will send immediately. You can also choose a future delivery time.

[jstanden]

Here's the guide on sending mail from automations: #23

[wbtittle]

Thank you.

…

On Mon, Jan 23, 2023 at 3:28 PM Jeff Standen ***@***.***> wrote: Here's the guide on sending mail from automations: #23 <#23> — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADGGR2MR7OOULIIZHSBKOLWT4HZ5ANCNFSM6AAAAAAUEBCYYE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Brad Tittle Tech Support