Skip to main content
Evonne Dao
Community Manager
February 4, 2026

FAQs: Email Trigger Best Practices

  • February 4, 2026
  • 6 replies
  • 168 views

Make the Email Trigger Visible

The best way to see if an email had sent or if there was an error is to make the email trigger visible on the form. This way, you can see exactly what was placed in the email without having to access the recipients email for proof. If, for some reason, it did not send this will also help notify you as you can verify the status.
 

 

11475400-FAQs_Email_Trigger_Best_Practices-upload_7796010483162604973.png

 

  1. Click the gear for the email trigger

  2. Uncheck the Hidden checkbox (it is default to be Hidden)

  3. Choose Apply

 

 

Email Trigger Statuses

 

11475400-FAQs_Email_Trigger_Best_Practices-upload_10402816717525768927.png

 

  1. This is the Email Trigger Status area. Please note, you can click it if it was Email Sent or Email Failed for further details.

If the email trigger is visible on the form, after every single save, you will then be able to see the email trigger on the form. Yes, that means on a brand new record (before the first save) you won't see it, but directly after saving it you will. After each save, you will then see the status of the email trigger and there are a few statuses to keep in mind:

 

  • Not Triggered: this means that the email was not send. This is generally not due to an error but usually because the email trigger didn't meet the proper criteria to send, for example, there was a filter on it that said to only send on record updates and if the Date field changed.

  • Email Sent: this means that the Email successfully left Apricot. This isn't the end of the emails journey through the web though! It next reaches SendGrid, Apricot's official email relay service. SendGrid will then send it via standard email protocol. It's possible that the email was blocked or bounced after SendGrid attempted to send it (this is not an Apricot error). You can read more about SendGrid at the bottom of this article.

  • Email Failed: this means that the email trigger was supposed to send the email (all criteria was met) but there was an error and it didn't even make it out of Apricot. You may click the error message to see additional details which may provide a hint as to why it failed. If it doesn't provide a hint to the failure please contact the Ongoing Support Team for further assistance. Please provide the URL to the record in question when doing so.

 

 

Trigger Event

The Trigger Event is the most common problem why an email trigger doesn't send. Generally, you will see "Not Triggered" in the Email Status every single time you save the record, even if it meets the criteria to send, if you forgot to set the Trigger Event. This tells Apricot if it should send an email only on record creation, only on record update, only on batch creation, or a combination thereof. At least one Trigger Event must be checked or an email will never send.
 

11475400-FAQs_Email_Trigger_Best_Practices-upload_16786587365651026858.png

 

  1. Click the gear for the Email Trigger

  2. Check one or more of the boxes

  3. Apply

 

Note that you can also set your Trigger Event to send an email when a specific field is updated.

 

Email Trigger fields are unique where that the record displays only the most recent status of an email trigger; reports also only show the most recent email status. Therefore, it's not accurate to look at a record (or a report) and see "Email Sent" or "Email Failed' or even "Not Triggered" and come to the conclusion that it is accurate. For example, let's take a look at some of these scenarios:

 

  1. You have an Email Trigger to send an email only upon Record Creation Let's then say that record was created and all filter criteria was met. The Email did send. But, then someone re-saves the record one more time. The Email Trigger Status now says Not Triggered

  2. You have an Email Trigger to send an email upon Record Updated only if the Date field is changed. The record is created, no email trigger is sent so our Status says Not Triggered, as expected. The record is updated, but the Date field was never changed, so our status still says Not Triggered The record is updated again, but this time the Date was changed, the record will now show Email Sent But, let's say someone saves the record yet again, the date did not change, the record will not show Not Triggered

 

The record will only show the status of the most resent save, but we can verify that the email was sent by by clicking 'View History' to view the Record History.

 

Let's say we have an Email Trigger that has the following criteria:

 

  • Send only on Record Updates

  • And, only if, Date = 6/24/2019

 

upload_5377684406668411221.png?expires=1770909300&signature=0138c3befdad5a926379458ab7bb2bb372a2d7266d79f821c96720683791012c&req=dSUhHsF8mIJeXPMW1HO4zfIBIYpP2%2BGYiKNfl%2BbM96NBgZ%2FXj6TkbhX0Dwe5%0AiNpgtIXsmyC9l8dBM7E%3D%0A

 

  1. Click Show History

 

upload_11780191021756559136.png?expires=1770909300&signature=b3d92861f3d7432b8f7fb702044776ddf9acd4bc96b448c7f90a51f471dbf716&req=dSUhHsF8mIJdW%2FMW1HO4zThzEhqq2A24Te%2FX8QgRwD9UA0QdtpByM2ovCguN%0A8jjbCiSIrAvroXiJ3NM%3D%0A

 

  1. Find the record history which should have triggered the email, you may need to go through multiple histories to find the record. Once you find it, click on it.

  2. Then, we can see if the email trigger was sent and we can see that it sent on 6/24/2019 as expected.

 

 

Email Trigger Tips and Tricks

  1. Email is not a secure form of communication. Please take this into consideration when deciding what information to send via an email trigger field.

  2. System fields (Record ID, Created By, Creation Date, Modified By, Modification Date and Assigned Programs) cannot be used in email trigger filters.

  3. An email is only sent to recipients listed in the Main tab of the Email Trigger properties, if all the field's configured conditions are met. The trigger does not automatically send an email to the user who created or edited the record.

  4. We use a 3rd party integration to send emails through Apricot on your behalf called SendGrid (see below for additional details). Customer Support can check to see if an email was sent, but SendGrid only saves email logs for 7 calendar days so you must contact us within that time for us to check. We cannot provide direct access to SendGrid. You may need to inform your recipients that they might need to allow-list the following email address if the emails are going to their spam folder: no-reply@socialsolutions.com

  5. Imports cannot be used to prompt an email trigger to send an email. Records must be manually created or updated in order to activate the email trigger.

  6. Email triggers cannot be used to send emails at a future time. They are triggered by an action and will only send upon creation/modification save.

  7. Images from Shared Files that are linked in the email body will not display in external email clients.

 

What Are Best Practices for Email Triggers in Apricot? | How Do I Set Up an Email Trigger in Apricot? | Why Isn’t My Email Trigger Sending in Apricot? | How Do I Customize Email Trigger Content in Apricot? | When Should I Use Email Triggers in Apricot? | How Do I Test Email Triggers in Apricot? | How Do I Troubleshoot Email Trigger Issues in Apricot?

6 replies

DB ADMIN
Explorer
May 29, 2026

Is there a best practice for size of attachment?

Rebekah Eslao
Community Manager
May 29, 2026

Hi ​@DB ADMIN!

 

Great question. The attachment size limit is 25MB, but here's what tends to work best:

  • Keep attachments as lean as possible—smaller files upload faster and help the system run smoothly
  • Compress PDFs or docs before attaching if its more than the limit

 

For more details on how attachments work in Apricot, check out the “Sending Attachments” part of this help article: 

 

Happy to help if you have more questions! 😊

Rebekah at Bonterra
Olga K
Explorer
August 10, 2026

We add personalizations to our email triggers. Is there a way to make the text searchable? (For example - if we wanted to pull up all the occasions when we wrote “pledge” in the personalization of an email trigger). Thank you.

AnnieNovacek
Community Manager
August 10, 2026

Hi ​@Olga K ! I want to be sure I am understanding what you are asking. Let me know if one of these sounds aligned with your goal, and feel free to share any more context to clarify.

When you say “pull up all the occasions” do you mean in a report? If so, the message in the email sent via one of these Triggers is not reportable. In Native reporting you can see if it triggered, but not further detail.

If you mean you want to trigger an email only when you include the word “pledge” in a given field, that should be doable. When configuring the Email Trigger field, go to the Filters tab and add this as one of the criteria. You should be able to choose “contains” if it’s an open text field for example. With that said, you may consider streamlining the process by adding a standardized way to ensure this is not missed such as an option field where your team can indicate that this was a pledge. Filters to trigger the email would work in a similar way, but this would ensure you aren’t relying on an open text field if you are worried someone might forget to use the right keyword. 

Note, when it comes to personalizing Email Triggers, including fields from the associated form is a great way to make sure what’s included in the message is relevant for that person. I would just be mindful that if you need different messages for different situations, you might consider separate Email Triggers with distinct filter criteria so the right message is sent. 

Olga K
Explorer
August 11, 2026

Thank you so much Annie. I appreciate your understanding of my awkwardly worded question and your responses. I was looking for the first option - reporting. However, when reading through what you wrote, I decided to check if the personalizations we add to the email triggers can be searchable - and they can be! Since they are the fields that would have “pledge” written into, that might be a solution for my original dilemma. Thanks again!