If you set the operation to POST, you should be able to provide a custom request template. You can use a string variable here, which can contain any GraphQL mutation request you need.
Example with export mapping. The following microflow builds a list of 2 configurations, uses an export mapping to convert it to json and then uses rest call to call a dummy rest http endpoint:
Domain model and message definition:
Export mapping:
Export mapping activity to generate json from list:
Rest call with the Graphql payload:
You probably need additional info in the query, probably easiest to handle in the export mapping.
Hi! I am working on exchanges between Mendix and CRM by using GraphQL. We can expect something from Mendix in the futur to offer a clean and easy way to integrate this kind of exchanges. But, for now, the fastest way is using JSON directly (that s means a java action) to be able to build the JSON structure, especially if you use variables because you will never be able to build your request directly with Mendix without knowing, per advance, what will be the JSON structure (mapping is not possible when you don t know what will be key-value pairs and also the data type / number, string, boolean).
If you work only with simple queries, you can use the default JSON export mapping provided by Mendix.