How to Setup ScreenConnect Trigger to Email You When Guest Connects

• This article that explains how to set up a ScreenConnect trigger to email you when a guest connects to your session.
• The article provides step-by-step instructions, screenshots, and examples for creating and testing the trigger, as well as some frequently asked questions and answers.

ScreenConnect is a remote support software that allows you to connect to any device from anywhere. It’s a great tool for providing technical assistance, troubleshooting issues, and collaborating with your clients or team members.

But what if you want to be notified by email when a guest connects to your session? This can be useful if you’re busy with other tasks and don’t want to miss any incoming requests. Or maybe you just want to keep track of who’s using your service and when.

Fortunately, ScreenConnect has a feature called triggers that lets you automate actions based on certain events. In this article, we’ll show you how to set up a trigger that will send you an email whenever a guest connects to your session.

What are ScreenConnect triggers?

Triggers are rules or recipes that can “fire” an action when a certain session event occurs. For example, you can create a trigger that will send a chat message to greet a customer when they connect to your session. Or you can create a trigger that will send an email to your manager when a session ends.

Triggers can also be integrated with extensions to provide additional notifications. For instance, you can use an extension to send a message to your HipChat room when a guest connects to your session.

To create and manage triggers, you need to access the administration page of your ScreenConnect server. You can do this by appending /admin to the end of your server URL. For example, if your server URL is https://example.screenconnect.com, then the administration page URL is https://example.screenconnect.com/admin.

On the administration page, click on the Triggers tab. Here, you can see the list of existing triggers and create new ones.

How to create a trigger that will email you when a guest connects

To create a trigger that will email you when a guest connects, follow these steps:

1. On the Triggers tab, click on the Add button at the top right corner.
2. Give your trigger a name and description. For example, “Email me when guest connects”.
3. In the Event Filter section, specify the conditions for the trigger to fire. For this example, we want the trigger to fire when the event type is Connected and the connection process type is Guest. The syntax for the filter looks like this:Event.EventType = 'Connected' AND Connection.ProcessType = 'Guest'
4. In the Action section, select Send Email from the drop-down menu.
5. In the To field, enter your email address or multiple addresses separated by commas.
6. In the Subject field, enter the subject line for your email. You can use placeholders like {Session.Name} or {Event.Data} to include dynamic information from the session or event.
7. In the Body field, enter the message for your email. You can also use placeholders here to customize your message.
8. Click on Save at the bottom right corner.

That’s it! You’ve successfully created a trigger that will email you when a guest connects to your session.

How to test your trigger

To test your trigger, you can either connect to your own session as a guest or ask someone else to do it for you. You should receive an email notification shortly after the connection is established.

How to edit or delete your trigger

If you want to edit or delete your trigger, you can do so from the Triggers tab on the administration page. Just click on the Edit or Delete button next to your trigger name.

Frequently Asked Questions

Here are some common questions and answers related to ScreenConnect triggers and email notifications.

Question: How can I change the sender address or name of the email notifications?

Answer: By default, ScreenConnect uses [email protected] as the sender address and ScreenConnect as the sender name for email notifications. If you want to change these settings, you need to configure an SMTP server for your ScreenConnect server.

To do this, go to the Administration page and click on the Mail tab. Here, you can enter the details of your SMTP server, such as host name, port number, user name, password, etc. You can also specify the sender address and name for your emails.

Question: How can I send email notifications to different recipients based on certain criteria?

Answer: If you want to send email notifications to different recipients based on certain criteria, such as session name, group name, or custom property value, you need to use an extension that supports conditional logic.

One such extension is called Conditional Emailer. It allows you to create multiple email templates and assign them to different conditions using expressions. You can download and install this extension from ScreenConnect’s extension marketplace.

Question: How can I troubleshoot email notifications if they are not working?

Answer: If you’re not receiving email notifications from your ScreenConnect server, there are a few things you can check:

• Make sure your trigger is enabled and has the correct event filter and action settings.
• Make sure your email address is correct and not blocked by spam filters or firewalls.
• Make sure your ScreenConnect server has internet access and can connect to your SMTP server (if you’re using one).
• Check the logs on your ScreenConnect server for any errors or warnings related to email notifications. You can find the logs in the Logs folder under your ScreenConnect installation directory.

Conclusion

ScreenConnect triggers are a powerful feature that can help you automate tasks and notifications based on session events. In this article, we showed you how to create a trigger that will email you when a guest connects to your session.

We hope you found this article helpful and learned something new. If you have any questions or feedback, feel free to leave a comment below.

Disclaimer: The content of this blog article is for informational purposes only and does not constitute professional advice. The author is not a licensed lawyer, doctor, or technical expert and does not claim to provide any legal, medical, or technical guidance. The information and opinions expressed in this article are based on the author’s personal research and experience and may not reflect the current state of the law or technology. The author does not guarantee the accuracy, reliability, completeness, or usefulness of the content and disclaims any liability for any errors, omissions, or damages arising from the use of the content. Readers are advised to consult a qualified professional before acting on any information or opinions contained in this article. The author may receive compensation from some of the links or products mentioned in this article, but this does not influence the author’s views or recommendations. The author is not affiliated with any of the websites or sources cited in this article.