Referencing User Configurations in Resources

To pass configurations to a resource, you'll need to define a parameter that contains the value of the configuration. You'll then need to reference that parameter in your vendor path. In this example, we're extending the Pardot element to GET email clicks. 

The vendor path requires an API version, which is different for every account and is stored in configurations.

Here, we add a parameter that accesses the `provider.version` configuration value and sets the path variable to `providerVersion`. We'll then remove the hardcoded version value and replace it with our path variable.