https://community.appian.com/discussions/f/integrations/14594/dynamic-queryparameter-names-and-valuesHi everyone, I&#39;m developing an integration with a tool called e-goi and I need to send information about users inside query parameter. I need to do this dynamically since I can have multiple users being sent at one time. I already did some tests thaten-USTelligent Community 12https://community.appian.com/thread/65439?ContentTypeID=1Wed, 27 Mar 2019 15:50:55 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b29265cd-60c0-426c-b538-334f6d85a2ecjosuv0001Hi Justin, thanks for replying.<br /> <br /> Yes, I am calling E-goi from Appian, and E-goi can receive posts, but the parameters are received as queryParameters, as you can see here <a href="https://api-docs.e-goi.com/api/v2/#addSubscriberBulk">api-docs.e-goi.com/.../</a><br /> <br /> Thanks for your help, I did not remember that the URL can be edited as an expression<div style="clear:both;"></div>https://community.appian.com/thread/65437?ContentTypeID=1Wed, 27 Mar 2019 15:41:26 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b2df775c-073d-4f0a-b46b-2b85c757b730Justin WattsI&#39;m making the assumption you are calling e-goi from Appian, though that&#39;s not clear to me from your post.<br /> <br /> Can e-goi receive POSTs? You could then put this into the body of your integration. Given the potential length of this URL, this may be a more robust solution anyways if you hit URL length limits.<br /> <br /> If not, then try to append your options directly in the URL of the integration object, rather than the Query Parameters fields (and you have no other parameters defined), I think Appian skips encoding based on the quick tests I did. However, this is not a great solution as encoding is a best practice in my mind. To me, the ideal state is for e-goi would be made to support encoded requests.<div style="clear:both;"></div>