Power Automate · Cloud flows: action inputs
Invalid type. Expected String but got Null.
Short answer
This Power Automate error means a field you reference is empty (null) and the action expects text. Wrap the reference in coalesce(field, '') or add a condition that checks for null first.
VerifiedLast verified
01Error text
Invalid type. Expected String but got Null.02Likely causes
- A field you're referencing is empty (null) and the action expects text.
03How to fix it
- Wrap the reference in
coalesce(field, ''). - Or add a condition to check for null first.
04Official documentation
→Related errors
- ExpressionEvaluationFailedExpressionEvaluationFailed in a Power Automate cloud flow: An expression failed to evaluate at runtime because the actual data didn't match what the expression expected. This error only occurs when the expression uses **dynamic values** (variables, trigger body, action outputs) that can't be checked at save time. The most likely fix is to add null checks, validate types.
- ContentConversionFailedContentConversionFailed in a Power Automate cloud flow: The flow couldn't convert data from one type to another between actions. The most likely fix is to use explicit type conversions.
- MissingRequiredPropertyMissingRequiredProperty in a Power Automate cloud flow: A required input field on an action or trigger is empty. The most likely fix is to fill in required fields.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs