A Power Apps custom connector calling an IFS Action that expects no request body (unlike other actions that do take a body) fails with 'error while deserializing contents' — Power Apps apparently won't submit an actual empty {} JSON body for an action configured with no parameters, which is what the action needs to succeed.

All FAQ questions / Integrations and APIs

Answer

Invoke a Power Automate 'flow' of type HTTP request from within the Power App instead of calling the IFS action connector directly — Power Automate's own HTTP action gives you full, explicit control over exactly what request body gets sent (including deliberately sending a literal {} body), sidestepping Power Apps' own connector behavior of omitting the body entirely for actions it thinks don't need one. This flow-based approach works specifically for no-body IFS Actions where the direct Power Apps connector call fails with a deserialization error.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions