![]() |
VOOZH | about |
Power Automate (Microsoft Flow) makes it easy to automate tasks that involve data from multiple systems, on premises or in the cloud. With the CData API Server, line-of-business users have a native way to create actions based on Salesforce Pardot triggers in Power Automate; the API Server makes it possible for SaaS applications like Power Automate to integrate seamlessly with Salesforce Pardot data through data access standards like Swagger and OData. This article shows how to use wizards in Power Automate and the API Server for Salesforce Pardot to create a trigger -- entities that match search criteria -- and send an email based on the results.
Follow the steps below to begin producing secure and Swagger-enabled Salesforce Pardot APIs:
The API Server runs on your own server. On Windows, you can deploy using the stand-alone server or IIS. On a Java servlet container, drop in the API Server WAR file. See the help documentation for more information and how-tos.
The API Server is also easy to deploy on Microsoft Azure, Amazon EC2, and Heroku.
After you deploy, provide authentication values and other connection properties by clicking Settings -> Connections in the API Server administration console. You can then choose the entities you want to allow the API Server access to by clicking Settings -> Resources.
Salesforce Pardot supports connecting through API Version, Username, Password and User Key.
The User Key of the current account may be accessed by going to Settings -> My Profile, under the API User Key row.
You will also need to enable CORS and define the following sections on the Settings -> Server page. As an alternative, you can select the option to allow all domains without '*'.
After determining the OData services you want to produce, authorize users by clicking Settings -> Users. The API Server uses authtoken-based authentication and supports the major authentication schemes. You can authenticate as well as encrypt connections with SSL. Access can also be restricted by IP address; access is restricted to only the local machine by default.
For simplicity, we will allow the authtoken for API users to be passed in the URL. You will need to add a setting in the Application section of the settings.cfg file, located in the data directory. On Windows, this is the app_data subfolder in the application root. In the Java edition, the location of the data directory depends on your operation system:
[Application] AllowAuthtokenInURL = true
You can use the built-in HTTP + Swagger connector to use a wizard to design a Salesforce Pardot process flow:
https://MySite:MyPort/api.rsc/@MyAuthtoken/$oas
Build the OData query to retrieve Salesforce Pardot data. This article defines the following OData filter expression in the $filter box:
ProspectAccountId eq '703'
See the API Server help documentation for more on filtering and examples of the supported OData.
You can now work with Prospects entities in your process flow. Follow the steps to send an automated email:
Learn more or sign up for a free trial:
CData API Server