A very powerful feature of Malcolm! is the ability to populate one or more values within a Workflow via the URL to the Workflow itself. Malcolm! also offers associated options around whether a user completing a Workflow can see or edit that value. This is extremely powerful if - for example - you want to pass into a Workflow information that lets you identify who has completed it - such as a customer ID or perhaps some other form of unique reference that lets you know what the information relates to (eg an order or transaction id) For example, let's say a customer has created an order with order ID 12345 and you need some further information to fulfil the order. Rather than send them a Workflow which asks them for their order ID as one of the questions (or relies on you manually linking the submitted Workflow with a completed order your side) you could send them a link in the format https://url.com/workflows/order-info-needed?orderid=12345 You can put values for multiple fields in the URL too eg https://url.com/workflows/order-info-needed?orderid=12345&anotherfield=abcde You can choose whether the user filling in the Workflow will see the Order ID repeated on their Workflow or not. If they can see it you can choose whether they can edit it or not. You can also choose what the descriptors in the URL (in the example above the "orderid" part) actually are. All these configurations are made by clicking on the individual element in the Workflow builder in MyMalcolm and scrolling to the "Settings" area. When the Workflow is submitted you will receive the Order ID (and any other fields you have completed via the URL) as part of the submitted information. When you combine the ability to populate fields by variables in the URL with the integration functionality of Malcolm! it becomes even more powerful as you could programmatically send out Workflows for completion (with some identifying information inserted via an auto generated URL) and then combine them with your other systems on submission via an integration or a webhook using the identifying information to link things together. This becomes a great way to send out surveys, create follow ups to marketing campaigns, extend the functionality you offer to "logged in" users etc etc - the possibilities are endless!

A very powerful feature of Malcolm! is the ability to populate one or more values within a Workflow via the URL to the Workflow itself. Malcolm! also offers associated options around whether a user completing a Workflow can see or edit that value. This is extremely powerful if - for example - you want to pass into a Workflow information that lets you identify who has completed it - such as a customer ID or perhaps some other form of unique reference that lets you know what the information relates to (eg an order or transaction id) For example, let's say a customer has created an order with order ID 12345 and you need some further information to fulfil the order. Rather than send them a Workflow which asks them for their order ID as one of the questions (or relies on you manually linking the submitted Workflow with a completed order your side) you could send them a link in the format https://url.com/workflows/order-info-needed?orderid=12345 You can put values for multiple fields in the URL too eg https://url.com/workflows/order-info-needed?orderid=12345&anotherfield=abcde You can choose whether the user filling in the Workflow will see the Order ID repeated on their Workflow or not. If they can see it you can choose whether they can edit it or not. You can also choose what the descriptors in the URL (in the example above the "orderid" part) actually are. All these configurations are made by clicking on the individual element in the Workflow builder in MyMalcolm and scrolling to the "Settings" area. When the Workflow is submitted you will receive the Order ID (and any other fields you have completed via the URL) as part of the submitted information. When you combine the ability to populate fields by variables in the URL with the integration functionality of Malcolm! it becomes even more powerful as you could programmatically send out Workflows for completion (with some identifying information inserted via an auto generated URL) and then combine them with your other systems on submission via an integration or a webhook using the identifying information to link things together. This becomes a great way to send out surveys, create follow ups to marketing campaigns, extend the functionality you offer to "logged in" users etc etc - the possibilities are endless!

Malcolm! now plugs into [Zapier](https://zapier.com). Zapier is an integration platform - [it connects thousands of apps to other apps.](https://zapier.com/apps) In the context of Malcolm! this means that when a Workflow is completed you can use our Zapier integration to route some or all of the data that has been collected from that Workflow through into Zapier and then in turn onto thousands of other apps or services. Here is how to set things up: 1. Firstly set up and publish a workflow in Malcolm! that collects the data you wish to move into other applications 2. In MyMalcolm go to the Settings Section, then Workflows, then Integrations, then click on Zapier 3. Sign up for an account at [Zapier](https://zapier.com) if you don't already have one - it is free - or login if you do have an account. 4. Accept the invite to Malcolm! 5. Still in Zapier, click "Make a Zap" 6. Your trigger app should be Malcolm! and you want it to trigger on a new Workflow completion so hit "Save + Continue" once you have selected this option 7. You now need to connect your Malcolm! instance to your Zapier account - click "Connect an Account" and follow the instructions. Once connected click "Save and Continue" 8. Choose a workflow then "Continue" 9. Wait for a sample to load and then click "Continue" 10. Choose an action App of your choice and configure as required - the exact process will vary from action App to action App but you are likely to need to agree some permissions and choose some options. Once done click "Save + Continue" or "Finish" 11. You will then be able to name your Zap and choose whether it is on or not 12. Back in MyMalcolm, if you find the Workflow you used in your Zap in the Library, select it, then go to Configure then Integrations you should be able to see Zapier has been added. You can turn the integation off here if you want and/or configure it to be conditional (for example to only run when certain choices have been made on a Workflow). Remember that Malcolm! always stores your data (which you can download anytime) - so if Zapier goes down or your integration doesn't seem to work properly no data will be lost. We are hugely excited about the possibilities opened up via Zapier - we hope you are too! If you have questions or need a hand setting things up just [contact us](https://support.malcolm.support/workflows/submit-support-ticket) and we'll be happy to help.

Malcolm! now plugs into [Zapier](https://zapier.com). Zapier is an integration platform - [it connects thousands of apps to other apps.](https://zapier.com/apps) In the context of Malcolm! this means that when a Workflow is completed you can use our Zapier integration to route some or all of the data that has been collected from that Workflow through into Zapier and then in turn onto thousands of other apps or services. Here is how to set things up: 1. Firstly set up and publish a workflow in Malcolm! that collects the data you wish to move into other applications 2. In MyMalcolm go to the Settings Section, then Workflows, then Integrations, then click on Zapier 3. Sign up for an account at [Zapier](https://zapier.com) if you don't already have one - it is free - or login if you do have an account. 4. Accept the invite to Malcolm! 5. Still in Zapier, click "Make a Zap" 6. Your trigger app should be Malcolm! and you want it to trigger on a new Workflow completion so hit "Save + Continue" once you have selected this option 7. You now need to connect your Malcolm! instance to your Zapier account - click "Connect an Account" and follow the instructions. Once connected click "Save and Continue" 8. Choose a workflow then "Continue" 9. Wait for a sample to load and then click "Continue" 10. Choose an action App of your choice and configure as required - the exact process will vary from action App to action App but you are likely to need to agree some permissions and choose some options. Once done click "Save + Continue" or "Finish" 11. You will then be able to name your Zap and choose whether it is on or not 12. Back in MyMalcolm, if you find the Workflow you used in your Zap in the Library, select it, then go to Configure then Integrations you should be able to see Zapier has been added. You can turn the integation off here if you want and/or configure it to be conditional (for example to only run when certain choices have been made on a Workflow). Remember that Malcolm! always stores your data (which you can download anytime) - so if Zapier goes down or your integration doesn't seem to work properly no data will be lost. We are hugely excited about the possibilities opened up via Zapier - we hope you are too! If you have questions or need a hand setting things up just [contact us](https://support.malcolm.support/workflows/submit-support-ticket) and we'll be happy to help.

integrations - Tags - Malcolm! Help & Support - browse our Frequently Asked Questions and support articles

Can I set Workflow values in a URL?

Yes - this is one of the features that makes Malcolm! Workflows super powerful!

integrations logic overview

100% found this useful

How do I use Zapier to connect Malcolm! to other applications or services I use?

Malcolm! now plugs into Zapier - find out how to use it here!

integrations MyMalcolm zapier

100% found this useful

Not many results?

Sorry we couldn't find many results related to your search.

Alternatively, why not browse our categories.

You are here

Can I set Workflow values in a URL?

How do I use Zapier to connect Malcolm! to other applications or services I use?

Not many results?

Upgrade your content

Hey there!