How to Create a Flow in Power Automate Connected to HubSpot using the HTTP Action
In this follow-up tutorial video, Devin Knight of Pragmatic Works demonstrates how to integrate Power Automate with HubSpot using the HTTP action. This is part two of a series, building on the previous video that covered creating a private app in HubSpot. This blog post summarizes how to securely connect Power Automate to the HubSpot API, make dynamic calls, and handle contact data intelligently.
Reviewing the HubSpot API Documentation
Devin begins by revisiting the HubSpot API documentation, focusing on how to interact with HubSpot’s contact search functionality. This is essential for knowing what parameters and headers are required to pass into Power Automate. The documentation allows users to:
- Understand HTTP request types (GET, POST, PUT)
- Use filters and parameters (e.g., search by email)
- Test requests using their access token
Setting Up the Power Automate Flow
The tutorial continues with the creation of a new flow in Power Automate. For the demo, Devin uses an instant cloud flow with a manual trigger, ideal for demonstration purposes but easily adaptable to other triggers (like new invoice events).
Using the HTTP Action
The core of this integration uses the HTTP action, which is a Premium Power Automate feature. Key configuration steps include:
- Method: Select
POSTto send the contact search request. - URI: Copy the endpoint from the HubSpot documentation for searching contacts.
- Headers:
Authorization: UseBearer YOUR_ACCESS_TOKENContent-Type: Typicallyapplication/json
- Body: Construct a JSON payload that includes filter parameters. Example:
{ "filterGroups": [{ "filters": [{ "propertyName": "email", "operator": "EQ", "value": "you@example.com" }] }], "limit": 1 }
Adding a Variable for Dynamic Email Search
To make the flow reusable, Devin demonstrates how to initialize a variable to store the email address. This allows for dynamic content in the HTTP request body. He shows how to insert the variable using Power Automate’s dynamic content panel.
Testing the Flow
After setting up the headers, body, and variables, Devin runs a manual test of the flow. The response from HubSpot returns key information such as:
- First and last name
- Contact’s HubSpot Object ID
- Email match status
Devin validates this by using the returned object ID to search directly in HubSpot, confirming that the correct contact data was retrieved.
Best Practices and Use Cases
While the demo uses hardcoded values for simplicity, Devin encourages following best practices such as renaming actions and storing tokens securely. Some potential real-world applications for this flow include:
- Checking if a contact exists before assigning a deal
- Creating new contacts if none exist
- Building more advanced workflows around contact status
Conclusion
This video effectively showcases how to bridge Power Automate with HubSpot’s API using the HTTP action. With dynamic inputs and API calls, users can customize workflows beyond the limitations of built-in integrations. The flow enables automation scenarios like lead verification, contact creation, and deal assignment with minimal code.
Don't forget to check out the Pragmatic Works' on-demand learning platform for more insightful content and training sessions on Power Automate and other Microsoft applications. Be sure to subscribe to the Pragmatic Works YouTube channel to stay up-to-date on the latest tips and tricks.
Sign-up now and get instant access
ABOUT THE AUTHOR
Devin Knight is a Microsoft Data Platform MVP, Microsoft Certified Trainer, and President of Pragmatic Works. He focuses on driving adoption of technology through learning. He is an author of nine Power Platform, Business Intelligence, and SQL Server books. He has been selected as a speaker for conferences like Power Platform Summit, PASS Summit, SQLSaturdays, and Code Camps for many years. Making his home in Jacksonville, FL Devin is a contributing member to several local user groups.
Free Community Plan
On-demand learning
Most Recent
private training

Leave a comment