Likewise, I am in a similar situation although with the subscription method now implemented in IFTTT leaving free subscribers with only two steps IFTTT has now been left as purely a set of connectors. There is another app - Automate - that I now use to handle most steps in any workflow, however it can push a notification to IFTTT with relevant values and content assigned to variables, expose IFTTT's internal services and deliver into them (or receive from them). It is quite an in-depth app with capabilities far beyond IFTTT but for someone with little coding background it enables within a few steps for the relevant values (assigned to Automate's individual flow's variables) to trigger IFTTT and use IFTTT's connectors to deliver the payload to any of it's connectors.
For instance, I'm using it at the moment to wait for an URL to be shared to a specific flow within Automate through android's share mechanism to the particular Automate 'Fiber' (Automate's terminology for flow), strip the title, media and text into separate entities, and deliver them concurrently as a notification trigger, then via IFTTT's MyCloud Home connectivity to be stored on my device / account. This could also work the other way round as google assistant can pass messages through IFTTT which Automate can pick up, do the heavy lifting and ultimately pass back to IFTTT's connectors to complete.
So, to cut a long story short - the detour is via Automate which has access to all android system services and is far more complex and capable than IFTTT, though simple enough to use some of it's capabilities as a bridge where IFTTT isn't
capable enough at all. It could all be done in Automate, however there would be a steep learning curve.