Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


TaskFlow provides clients with their own email server which is hosted by us on our cloud infrastructure. If your TaskFlow URL is structured as: https://<name> then you'll have a corresponding email server at *@<name>


For example: has an email server * You can send an email to and that email will create a new lead in the Sales Pipeline. Try it out on our demo website.


  • Emails will immediately be available in TaskFlow whereas there is a potential delay of 10 minutes when you use your own email server
  • There are no hourly limits when sending large outbound campaigns whereas most email servers will put a limit of about 500 emails per hour


What if I already have my own email accounts?

If you already own an email account such as or, all you need to do as add a forwarding rule that will forward all emails to

How do I authorize TaskFlow's email server?

Not all mail servers are allowed to send emails on your company's behalf. You can check which mail servers are authorized by running the following command in terminal, or by using an online SPF checker such as

For example:

Code Block
Johnnys-MacBook-Pro:~ dig +short -t TXT
"v=spf1 mx a -all"

The above example is typically what your company's domain's SPF record looks like if you are using Outlook. In simple terms, it means that the email server at is granted permission to send emails on your company's ( behalf.

You will need to amend your domain's current SPF record and include "". After doing this, your domain's SPF record should look like this:

Code Block
Johnnys-MacBook-Pro:~ dig +short -t TXT
"v=spf1 mx a -all"

Please note, that after making this change, it may take up to 24 hours for the change to take effect.