other-emerald
other-emerald17mo ago

Failing to get API response from Make.com

I've tried everything I could find online but I think I'm doing something wrong. I'm getting a successful pass (200) and make.com scenario runs with no issues, but for some reason I am not capturing the reponse back in VF. Attached is how I set up my API block in VF. Screenshots from Make.com in the first comment 👇
No description
No description
No description
No description
4 Replies
Tico | Voiceflow Assistant
Based on your description, it seems like you're having trouble capturing the response from the API call in Voiceflow. Here are some steps you can follow to troubleshoot this issue: 1. Check the Capture Response section: In the API block, there's a section called "Capture Response". Here, you need to specify the path to the data you want to capture from the API response. The path should start with "response", followed by the keys leading to the data. For example, if your API response is {"data": {"name": "Voiceflow"}}, the path to capture the name would be response.data.name. 2. Assign the captured data to a variable: Once you've specified the path, you need to assign the captured data to a variable. This is done in the line below the path in the "Capture Response" section. The variable can be any variable you've created in your project. 3. Use the variable in your project: After capturing the data and assigning it to a variable, you can use this variable in your project. For example, you can use a Speak block to say the data: "The name is {variable}". 4. Test the API call: Use the "Send Request" button in the API block to test the API call. If it's successful, you should see the data you're trying to capture in the response. 5. Check the API documentation: Make sure you're correctly following the API documentation provided by Make.com. The documentation should tell you the correct endpoint, request type (GET, POST, etc.), and any necessary headers, body, or parameters. 6. Check for errors: If you're still having trouble, check the API block for any error messages. These can give you clues about what might be going wrong. Remember, the key to successfully capturing API responses in Voiceflow is to correctly specify the path to the data in the "Capture Response" section and to assign this data to a variable. Once you've done this, you can use the variable anywhere in your project.
other-emerald
other-emeraldOP17mo ago
Here's the screenshot from make.com
No description
other-emerald
other-emeraldOP17mo ago
ok per this response I dug around in the make documentation. I added the "HTTP Make API Key Auth request module" but I think I'm still doing something wrong... Any make.com experts here?
Tico | Voiceflow Assistant
It seems like you're trying to integrate the Make API with Voiceflow, but you're encountering some issues. To help you out, let's go over the basic steps you need to follow: 1. Obtain the Dialog Manager API Key: All requests to any Knowledge Base APIs require a Dialog Manager API Key. To obtain this key, go to the Integration tab on the project you uploaded data sources to and click the "Copy API key" button. 2. Use the API Key for Authorization: The Dialog Manager API Key is used for authorization. You need to pass this key in the Authorization header of each request. The format should be: Authorization: VF.DM.YOUR_API_KEY. 3. Make the API Request: Depending on what you're trying to achieve, you'll need to make the appropriate API request. For example, if you want to retrieve a list of documents, you would use the GET Document List Knowledge Base API. If you want to retrieve a specific document, you would use the GET Document Chunk Retrieval API. Remember, each API request may require different parameters. For example, the GET Document List API allows you to filter the document list by type (url, pdf, text, docx) and also allows you to include or exclude certain tags. If you're still having trouble, it might be helpful to review the API documentation again to ensure you're not missing any steps. Also, make sure that the API key you're using is correct and that you're passing it in the correct format in the Authorization header.

Did you find this page helpful?