How to Retrieve Data from Make.com to Pingstreams
If you are familiar with Make, you know how this platform allows you to create various automations. The good news is that you can easily connect your chatbot to Make and send and receive data from it.
In today’s tutorial, we will go through the process of receiving data from Make to our bot in Pingstreams. This integration opens up endless possibilities for data retrieval, processing, and automation.
To do this, we need to create a free account in Make and then connect it to our Pingstreams project.
Let’s dive in!
Use Cases for Data Retrieval
Section titled “Use Cases for Data Retrieval”Before we start, here are some powerful use cases for this integration:
- Customer data lookup from CRM systems
- Product information retrieval from databases
- Order status checking from e-commerce platforms
- Real-time inventory updates
- User authentication and verification
- Dynamic content generation
Make Configuration
Section titled “Make Configuration”Head to the Make dashboard and go to the Scenario section to create our flow.
For this automation, we need two modules: Custom Webhook and Webhook Response.
Setting Up the Custom Webhook
Section titled “Setting Up the Custom Webhook”As you can see in the image below, I have added the first module and copied the webhook address, which we will use later in the Pingstreams design studio.

Configuring the Webhook Response
Section titled “Configuring the Webhook Response”Then, add the other module - Webhook Response. In the Body section, I inserted a short message, but it could be in a different format like a piece of code or anything else.

Advanced Response Examples
Section titled “Advanced Response Examples”You can configure the webhook response to return various data formats:
Simple Text Response:
Section titled “Simple Text Response:”{
"message": "Hello from Make!",
"timestamp": "{{now}}"
}Customer Data Response:
Section titled “Customer Data Response:”{
"customer": {
"name": "{{customer.name}}",
"email": "{{customer.email}}",
"status": "{{customer.status}}",
"lastOrder": "{{customer.lastOrder}}"
}
}Product Information Response:
Section titled “Product Information Response:”{
"product": {
"id": "{{product.id}}",
"name": "{{product.name}}",
"price": "{{product.price}}",
"availability": "{{product.stock}}"
}
}Save the scenario and activate it.
That’s all for Make. Now we need to get back to the Pingstreams dashboard.
Pingstreams Configuration
Section titled “Pingstreams Configuration”Head to the Pingstreams dashboard and then from the Bot section, enter the Design Studio.
Setting Up the Web Request Action
Section titled “Setting Up the Web Request Action”For this example, I used a button and connected it to Web Request, which you can find among the Integration actions.
Click on the Web Request block and paste the webhook URL which we copied from the Make dashboard.

Understanding Response Attributes
Section titled “Understanding Response Attributes”In the Assigned section, you can see three attributes:
- Result: Contains the successful response data
- Status: HTTP status code of the request
- Error: Contains error information if the request fails
Creating Response Paths
Section titled “Creating Response Paths”I will create two paths, one for Results and one for Error, as you see in the image below.

Testing the Integration
Section titled “Testing the Integration”Now it’s time to check our integration. As you can see in the image below, data from Make has been successfully transferred to Pingstreams.

Advanced Use Cases and Examples
Section titled “Advanced Use Cases and Examples”This integration can help you retrieve information from different sources to your Pingstreams bot. This information can be a user’s name, tracking code, product ID, or anything else.
Customer Support Bot Example
Section titled “Customer Support Bot Example”User: "What's the status of my order #12345?"
Bot: [Triggers Web Request to Make]
Make: [Queries order database, returns status]
Bot: "Your order #12345 is currently in transit and will arrive tomorrow!"Product Catalog Bot Example
Section titled “Product Catalog Bot Example”User: "Tell me about the iPhone 15"
Bot: [Triggers Web Request to Make]
Make: [Retrieves product data from inventory system]
Bot: "iPhone 15 - $799, Available in Blue/Pink/Black. In stock: 50 units"User Authentication Example
Section titled “User Authentication Example”User: "I need to reset my password"
Bot: [Triggers Web Request with user email]
Make: [Validates user in CRM, generates reset token]
Bot: "Password reset link sent to your email!"Advanced Configuration Options
Section titled “Advanced Configuration Options”Dynamic Data Sending
Section titled “Dynamic Data Sending”You can send user-provided data to Make for processing:
In the Web Request body parameters:
Section titled “In the Web Request body parameters:”{
"userId": "{{userId}}",
"query": "{{userMessage}}",
"context": "{{conversationContext}}"
}Multiple Data Sources Integration
Section titled “Multiple Data Sources Integration”Configure Make to pull data from multiple sources:
- CRM System (Salesforce, HubSpot)
- Database (MySQL, PostgreSQL)
- API Services (Payment gateways, shipping providers)
- Cloud Storage (Google Drive, Dropbox)
- E-commerce Platforms (Shopify, WooCommerce)
Response Processing
Section titled “Response Processing”Handle different types of responses in Pingstreams:
JSON Response Processing:
Section titled “JSON Response Processing:”- Parse nested objects using dot notation
- Extract arrays and loop through data
- Conditional responses based on data values
Error Handling Strategies:
Section titled “Error Handling Strategies:”- Graceful degradation for API failures
- Fallback responses for timeout scenarios
- User-friendly error messages
Performance Optimization
Section titled “Performance Optimization”Best Practices for Speed:
Section titled “Best Practices for Speed:”-
Cache Frequently Requested Data
- Store common responses in Make
- Use conditional logic to avoid repeated API calls
- Implement time-based cache invalidation
-
Optimize Make Scenarios
- Minimize the number of operations
- Use filters to process only relevant data
- Implement parallel processing where possible
-
Efficient Data Transfer
- Send only necessary data in requests
- Compress large responses when possible
- Use pagination for large datasets
Security Considerations
Section titled “Security Considerations”Webhook Security:
Section titled “Webhook Security:”- Use HTTPS endpoints for all webhook URLs
- Implement authentication where sensitive data is involved
- Validate incoming requests to prevent abuse
- Log all interactions for audit purposes
Data Protection:
Section titled “Data Protection:”- Encrypt sensitive data in transit and at rest
- Implement rate limiting to prevent abuse
- Use secure API keys and rotate them regularly
- Follow GDPR/privacy compliance requirements
Troubleshooting Guide
Section titled “Troubleshooting Guide”Common Issues and Solutions:
Section titled “Common Issues and Solutions:”Webhook Not Triggering:
Section titled “Webhook Not Triggering:”- ✅ Check webhook URL is correctly copied
- ✅ Verify Make scenario is active
- ✅ Test webhook manually from Make interface
- ✅ Check Pingstreams bot is published
Data Not Returning:
Section titled “Data Not Returning:”- ✅ Verify Make response format matches expected structure
- ✅ Check for API authentication issues
- ✅ Review Make execution logs for errors
- ✅ Validate JSON response format
Timeout Issues:
Section titled “Timeout Issues:”- ✅ Optimize Make scenario execution time
- ✅ Implement asynchronous processing for long operations
- ✅ Use pagination for large data sets
- ✅ Add timeout handling in Pingstreams
Debugging Tools:
Section titled “Debugging Tools:”-
Make Execution History
- Review each operation step
- Check input/output data
- Identify bottlenecks
-
Pingstreams Test Mode
- Use bot testing interface
- Monitor variable values
- Track conversation flow
-
Network Monitoring
- Use browser developer tools
- Monitor webhook response times
- Check for failed requests
Monitoring and Analytics
Section titled “Monitoring and Analytics”Key Metrics to Track:
Section titled “Key Metrics to Track:”- Response times for data retrieval
- Success rates of webhook calls
- Error frequencies and types
- User satisfaction with bot responses
- Data freshness and accuracy
Setting Up Alerts:
Section titled “Setting Up Alerts:”-
Make Scenario Monitoring
- Email notifications for failures
- Slack alerts for critical issues
- Dashboard for performance metrics
-
Pingstreams Analytics
- Conversation success rates
- User drop-off points
- Response time analytics
Scaling the Integration
Section titled “Scaling the Integration”Enterprise Considerations:
Section titled “Enterprise Considerations:”-
High Availability Setup
- Multiple webhook endpoints
- Failover mechanisms
- Load balancing
-
Data Consistency
- Implement proper caching strategies
- Handle concurrent requests
- Ensure data synchronization
-
Performance Monitoring
- Set up comprehensive logging
- Monitor API rate limits
- Track resource usage
Conclusion
Section titled “Conclusion”This integration between Make.com and Pingstreams creates powerful possibilities for:
- Dynamic data retrieval from multiple sources
- Real-time information processing
- Automated business workflows
- Enhanced user experiences
- Scalable automation solutions
The combination of Make’s automation capabilities with Pingstreams’ conversational AI creates a robust system that can handle complex data operations while maintaining a smooth user experience.
Hope you find it helpful!
In case you need support in implementing this integration, please contact us via our support team.
To read more about Pingstreams capabilities, you can visit our website.
To get started for free with Pingstreams, click here.
Ready to implement this integration? Start by creating your Make.com scenario, then follow the steps to connect it with your Pingstreams bot for powerful data-driven conversations!