<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>mess on asdfasdfasdfasdfddd</title><link>https://academy.test.quriobot.com/tags/mess/</link><description>Recent content in mess on asdfasdfasdfasdfddd</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://academy.test.quriobot.com/tags/mess/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting too many (empty) notifications?</title><link>https://academy.test.quriobot.com/response-connections-integrations/getting-too-many-empty-notifications/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://academy.test.quriobot.com/response-connections-integrations/getting-too-many-empty-notifications/</guid><description>By default, we have switched the Notifications (on the Notifications tab) and for some templates, we also added a Response Connection Email type.
But sometimes you are just getting too many, sometimes empty, notifications and/or responses.
You can make use of the condition setting to avoid empty notifications (like only when an email address or telephone number was added):
Same approach applies for the response connections:
Note: The Response connection for email was used in this example, but this can, of course, be used on any of the Response Connection types</description></item></channel></rss>