# Using the Testing Features in Workflows

Testing a workflow is an important step for ensuring the successful implementation of automation. Here are some guidelines on how to use testing features in Workflows.

***Note:** While these methods are available for basic functionality. Testing a workflow organically as if the contact is real and setting off the trigger is the best method for trial testing a workflow*

You can add a contact to a workflow manually from the contact card of any lead and depending on the actions inside it may not behave as expected without using the appropriate trigger. You can also have a triggerless workflow when testing with the same result. Please review the articles in the help library on appointment triggers and order submissions for further detail.

**Part 1:** Awareness of the Workflow Setting Allow Multiple

If you are testing with a test contact please be aware of the Allow Multiple Setting in the settings tab of automations. You will need to start with a fresh contact when testing multiple times or allow this setting temporarily or otherwise.

{% embed url="<https://lh3.googleusercontent.com/FclmMkK-AjRycVlV7IICi9cP-uP9F5tPqumbaoGdGdnjmP5hv9xM9yJVHUigXxvsT4eIe-oMrQDlI7aZ2rnBDwW4Y4bpljPVQ3UDkWfOC0EanfFlEGAOe_Jk2BAZuIaQVBiz96rlTBGEJO4jzeDq_YM>" %}

**Part 2:** Testing the SMS action

When you add the SMS action to a workflow there is a Send Test SMS button where you can run a basic test of the message. This feature is also available with the Manual SMS action.

***Note:** Keep in mind that links will not send correctly when testing with this button and the same applies to custom values.*

***Note:** In general links will typically be blocked unless it is the full URL when sending SMS. Phone number setup will need to be completed for this to work and regional limitations will apply to tests as well. Spam messages will potentially be blocked by providers as well. Please review help articles on this matter.*

{% embed url="<https://lh5.googleusercontent.com/cTSBoVQS6ZtlV3jB0aPZ5-6zrVPQxYF7bC8VpPhrY9oE43RhDD1LWUF20sT7bXLOVt29HqnTKjdZgTQwJuXxWNw5q9KTwK4LdSe19Xpxlj8XaQRuyaYMONyQnZ7ZVSdSwUssKQ5uO7WrMYtOziIcbvg>" %}

**Part 3:** Testing the Email Action

When adding the Email action to a workflow there is a Send Test Mail button where you can run a basic test of the email.

***Note:** This button will commonly break links and not populate custom values correctly or at all*

***Note:** Test with a different email address than the sending address or it will commonly go to spam or trigger other error messages.*

{% embed url="<https://lh4.googleusercontent.com/EF7mUNWCpTCixtNMK45FX4P-qtTiuN-pZ9cLLEI3FhB6wX-ArHpE4zJYEKnlS2ohWEqDCWKGaSQR6kCOtFDtxXYoknsC_HA7F2EXNNFw9J9o3a0iM5oIUq9tIsFZ-PWsbxeY_sOL0SBFxsxsfUMYwOg>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/using-the-testing-features-in-workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.