DEV Community: Shivam Automations

Canvas LMS 'Get a Submission' module

Shivam Automations — Mon, 08 Jun 2026 03:23:48 +0000

Resolving Canvas LMS 'Get a Submission' Module Errors: A Step-by-Step Guide

Overview

The Canvas LMS 'Get a Submission' module is a crucial component for educators and administrators to track student progress and assignments. However, when integrated with automation tools like Make.com, errors can occur due to missing or incorrect Course ID, Assignment ID, or User ID. This guide provides a comprehensive solution to resolve the "Couldn't find the Canvas resource in module 1, Get submission" error, ensuring seamless integration between Canvas LMS and Make.com.

Error Diagnostic

The core error "Couldn't find the Canvas resource in module 1, Get submission" is typically caused by incorrect or missing Course ID, Assignment ID, or User ID in the Get a Submission module for Canvas LMS. This can be attributed to various factors, including:

Incorrect configuration of the Canvas LMS API
Missing or outdated Course ID, Assignment ID, or User ID
Insufficient permissions or access rights to the Canvas LMS resource

Step-by-Step Resolution

Step 1: Verify Canvas LMS API Configuration

Ensure that the Canvas LMS API is correctly configured in Make.com, with the correct API key, base URL, and authentication method.

Step 2: Validate Course ID, Assignment ID, and User ID

Verify that the Course ID, Assignment ID, and User ID used in the Get a Submission module are correct and up-to-date. Check the Canvas LMS dashboard to confirm the IDs.

Step 3: Configure the Get a Submission Module

Reconfigure the Get a Submission module in Make.com, ensuring that the correct Course ID, Assignment ID, and User ID are used. Save the changes and test the module.

Step 4: Verify the Integration

Test the integration by running the scenario and verifying that the Get a Submission module retrieves the correct submission data from Canvas LMS.

Next Steps

To avoid manual setup and potential errors, deploy the flow directly using Make.com. Register for a Make.com account today and streamline your Canvas LMS integration: https://www.make.com/en/register?pc=shivamautomations

Frequently Asked Questions

Q: What is the most common cause of the "Couldn't find the Canvas resource in module 1, Get submission" error? A: The most common cause is incorrect or missing Course ID, Assignment ID, or User ID in the Get a Submission module.
Q: How can I verify the Course ID, Assignment ID, and User ID in Canvas LMS? A: Check the Canvas LMS dashboard to confirm the IDs, or contact your Canvas LMS administrator for assistance.
Q: Can I use a custom script to resolve the error? A: Yes, you can use a custom script to resolve the error, but it is recommended to use the built-in Make.com modules for a more streamlined and efficient integration.

Simplest way to let OpenAI search an external legal API during a workflow?

Shivam Automations — Mon, 08 Jun 2026 03:23:25 +0000

Integrating OpenAI with External Legal API: A Step-by-Step Guide to Seamless Workflow Automation

Overview

The integration of OpenAI with external APIs is a common requirement in various workflows, especially those involving legal research and document analysis. However, setting up this integration can be challenging, particularly when using workflow automation tools like Make.com. This guide aims to provide a comprehensive solution to the issue of integrating OpenAI with an external legal API during a workflow, using Make.com as the automation platform.

Error Diagnostic

The error diagnostic for this issue reveals that the primary challenge lies in establishing a seamless connection between OpenAI and the external legal API. The absence of a direct integration module in Make.com for this specific use case necessitates a custom approach. The software systems involved include Make.com, OpenAI, and Gmail, with the core error being the inability to search the external legal API directly from OpenAI during the workflow execution.

Step-by-Step Resolution

Step 1: Setting Up the External Legal API Connection in Make.com

To begin, create a new module in Make.com for the external legal API. This involves adding the API endpoint, authentication details, and any other required parameters to establish a connection.

Step 2: Configuring the OpenAI Module in Make.com

Next, add an OpenAI module to your Make.com workflow. This module will be used to interact with the OpenAI API, allowing you to perform searches and other operations.

Step 3: Creating a Custom Integration Using Make.com's HTTP Module

Since a direct integration is not available, use Make.com's HTTP module to create a custom request to the external legal API. This request will be triggered by the OpenAI module, passing any necessary parameters for the search query.

Step 4: Mapping Response Data and Verifying the Integration

After setting up the custom integration, map the response data from the external legal API to the required format for your workflow. Verify the integration by testing the workflow and ensuring that the search results from the external legal API are correctly retrieved and processed by OpenAI.

Next Steps

To streamline your workflow automation and avoid manual setup complexities, consider deploying your flow directly using Make.com. By registering through our affiliate link (https://www.make.com/en/register?pc=shivamautomations), you can leverage the full potential of Make.com's automation capabilities, including seamless integrations with OpenAI and other services.

Frequently Asked Questions

Q: What if my external legal API requires specific authentication headers or query parameters? A: You can configure these details within the HTTP module in Make.com, ensuring that your custom integration request is properly formatted and authenticated.
Q: Can I use this approach for integrating OpenAI with other external APIs, not just legal ones? A: Yes, the steps outlined in this guide can be adapted for integrating OpenAI with various external APIs, provided you have the necessary API endpoints and authentication details.
Q: How do I handle errors or rate limits when searching the external legal API? A: Make.com provides features for error handling and rate limiting. You can configure your workflow to retry failed requests, handle errors gracefully, and implement rate limiting to avoid exceeding API usage limits.

Need help with integrating Whatsapp with Make

Shivam Automations — Mon, 08 Jun 2026 03:23:01 +0000

Resolving Whatsapp Integration Issues with Make.com: A Step-by-Step Guide

Overview

Make.com and Whatsapp are two powerful tools used in B2B automation, enabling businesses to streamline their workflows and enhance customer engagement. However, users often encounter issues when integrating Whatsapp with Make.com, resulting in failed input reception and stuck flows. This Standard Operating Procedure (SOP) aims to provide a comprehensive solution to resolve the Whatsapp integration issue with Make.com.

Error Diagnostic

The core error "Failed to receive input and flow gets stuck on the Whatsapp phase" is often caused by a potential issue with the API connection or authentication between Make.com and Whatsapp. This can be attributed to incorrect API credentials, insufficient permissions, or misconfigured Whatsapp Business API settings. To resolve this issue, it is essential to identify and address the root cause of the problem.

Step-by-Step Resolution

Step 1: Verify Whatsapp Business API Settings

Ensure that the Whatsapp Business API is properly set up and configured. Check the Whatsapp Business API dashboard to confirm that the API is enabled and the necessary permissions are granted.

Step 2: Check API Connection and Authentication

Verify that the API connection between Make.com and Whatsapp is secure and authenticated. Ensure that the API credentials, such as the API key and secret, are correct and up-to-date.

Step 3: Configure Make.com Module

Configure the Make.com module for Whatsapp by providing the necessary API credentials and settings. Ensure that the module is properly connected to the Whatsapp Business API.

Step 4: Test and Verify the Integration

Test the integration by sending a message from Make.com to Whatsapp. Verify that the message is received successfully and the flow is executed as expected.

Next Steps

To avoid manual setup and potential errors, we recommend deploying the flow directly using Make.com. Register for a Make.com account using our affiliate link: https://www.make.com/en/register?pc=shivamautomations, and take advantage of the streamlined integration process.

Frequently Asked Questions

Q: What are the prerequisites for integrating Whatsapp with Make.com? A: To integrate Whatsapp with Make.com, you need to have a Whatsapp Business API account and a Make.com account.
Q: How do I troubleshoot API connection issues between Make.com and Whatsapp? A: You can troubleshoot API connection issues by checking the API credentials, verifying the API connection, and ensuring that the necessary permissions are granted.
Q: Can I use a custom script to integrate Whatsapp with Make.com? A: Yes, you can use a custom script to integrate Whatsapp with Make.com, but it is recommended to use the pre-built Make.com module for a more streamlined and secure integration.

Shopify Watch Orders only works when manually started — how to process new paid orders automatically?

Shivam Automations — Mon, 08 Jun 2026 02:38:44 +0000

Resolving Shopify Watch Orders Automation: A Step-by-Step Guide to Processing New Paid Orders Automatically

Overview

The Shopify Watch Orders trigger is a crucial component in automating order processing for e-commerce businesses. However, users often encounter issues with this trigger, where it only works when manually started, failing to pick up new orders automatically. This Standard Operating Procedure (SOP) aims to resolve this issue, providing a comprehensive guide on configuring the Shopify Watch Orders trigger using Make.com, Shopify, and Google Sheets.

Error Diagnostic

The core error lies in the Shopify Watch Orders trigger's inability to reliably pick up new orders automatically, returning 'The module didn’t return any new data' when using Run once. The root cause is likely due to polling behavior or incorrect setup of the Shopify Watch Orders trigger, possibly resulting from rate limiting or incorrect configuration of Watch by: Creation date and Order limit. The software systems involved include Make.com, Shopify, and Google Sheets, which are commonly used for B2B integrations.

Step-by-Step Resolution

Step 1: Configure Shopify Watch Orders Trigger

To resolve the issue, start by configuring the Shopify Watch Orders trigger in Make.com. Ensure that the trigger is set up to watch for new orders by creation date and set the order limit to a reasonable number to avoid rate limiting.

Step 2: Set Up Webhook in Shopify

Set up a webhook in Shopify to notify Make.com of new orders. This will enable real-time updates and prevent the need for polling. Configure the webhook to send notifications to Make.com for new orders.

Step 3: Create a Scenario in Make.com

Create a new scenario in Make.com, adding the Shopify Watch Orders trigger as the starting point. Configure the trigger to fetch new orders and add a filter to only process paid orders.

Step 4: Integrate with Google Sheets

Integrate the scenario with Google Sheets to store and process order data. Use the Google Sheets module in Make.com to create a new sheet or update an existing one with the order data.

Step 5: Verify the Setup

Verify the setup by running the scenario manually and checking if new orders are being processed automatically. Monitor the scenario's performance and adjust the configuration as needed to ensure reliable and efficient order processing.

Next Steps

To skip the manual setup and deploy the flow directly, register for a Make.com account using our affiliate link: https://www.make.com/en/register?pc=shivamautomations. This will enable you to automate your Shopify order processing and integrate with Google Sheets seamlessly.

Frequently Asked Questions

Q: What is the recommended order limit for the Shopify Watch Orders trigger? A: The recommended order limit depends on your store's order volume and the frequency of updates. A lower limit can help avoid rate limiting, but may require more frequent updates.
Q: Can I use Zapier instead of Make.com for this integration? A: Yes, Zapier can be used as an alternative to Make.com for integrating Shopify with Google Sheets. However, Make.com offers more advanced features and customization options.
Q: How do I troubleshoot issues with the Shopify Watch Orders trigger? A: To troubleshoot issues, check the trigger's configuration, ensure that the webhook is set up correctly, and verify that the scenario is running without errors. You can also check the Make.com logs for more detailed error messages.

Make.community Expert

Shivam Automations — Mon, 08 Jun 2026 02:38:21 +0000

B2B Integration Solution for Seamless Automation with Make.com and Zapier

Overview

The modern B2B landscape involves a myriad of software systems, including Make.com, GoHighLevel, HubSpot, Zoho, Airtable, Pipedrive, and Zapier, aimed at streamlining business operations. However, integrating these systems can be daunting, leading to inefficiencies and missed opportunities. This SOP addresses the challenge of integrating multiple B2B software systems, focusing on a promotional post scenario where no error is reported, but automation and integration are desired for enhanced productivity.

Error Diagnostic

The diagnostic analysis reveals no core error but indicates a need for integration to automate workflows across different platforms. The root cause guess suggests that the current setup lacks automation, leading to manual intervention and potential data inconsistencies. The software list includes:

Make.com
GoHighLevel
HubSpot
Zoho
Airtable
Pipedrive
Zapier Each of these tools offers unique functionalities, but their isolated use can lead to data silos and inefficient workflows.

Step-by-Step Resolution

Step 1: Choose an Integration Platform

Select either Make.com or Zapier as your integration platform. Both offer a wide range of connectors for the listed software systems. For this example, we'll use Make.com due to its robust features and ease of use.

Step 2: Configure Your Modules

Create a Scenario: In Make.com, start by creating a new scenario. This involves defining the trigger (e.g., new contact in HubSpot) and the action (e.g., creating a new row in Airtable).
Connect Your Apps: Connect the necessary apps (e.g., HubSpot, Airtable) to Make.com. This step requires authentication and often involves generating API keys or tokens.

Step 3: Map Your Data

Map the data fields from the trigger app to the action app. For instance, if you're moving data from HubSpot to Airtable, you'll need to map the contact fields (name, email, phone number) from HubSpot to the corresponding fields in Airtable.

Step 4: Test Your Scenario

Before deploying your scenario, test it to ensure data is being transferred correctly and that there are no errors. Make.com provides a testing feature that allows you to run your scenario with sample data.

Step 5: Deploy and Monitor

Once your scenario is tested and validated, deploy it. Make.com will then automatically run your scenario based on the trigger you've set. It's crucial to monitor the performance of your scenario, especially in the initial stages, to catch and fix any unexpected issues.

Next Steps

To skip the manual setup and directly deploy the flow, consider using Make.com. By registering through our affiliate link, https://www.make.com/en/register?pc=shivamautomations, you can access a streamlined integration process tailored to your B2B automation needs.

Frequently Asked Questions

Q: What if I encounter an error during the integration process? A: Make.com and Zapier offer extensive documentation and support forums. You can also reach out to their support teams for personalized assistance.
Q: Can I integrate more than two software systems at once? A: Yes, both Make.com and Zapier support multi-app integrations, allowing you to automate complex workflows across several platforms.
Q: How secure is my data during the integration process? A: Make.com and Zapier prioritize data security, using encryption and secure authentication methods to protect your data during transfer and storage.

Quickbooks deposit triggers Streak

Shivam Automations — Sun, 07 Jun 2026 17:47:27 +0000

Resolving Quickbooks Deposit Triggers Streak API Sync Failure

Overview

The integration of Quickbooks, Streak, and Gmail is crucial for many businesses to streamline their financial and customer relationship management processes. However, users often encounter API sync failures between Quickbooks and Streak, hindering the automation of deposit triggers. This Standard Operating Procedure (SOP) aims to address the root cause of this issue, which is often attributed to insufficient technical expertise in implementing the integration.

Error Diagnostic

The API sync failure between Quickbooks and Streak can be attributed to several factors, including incorrect API credentials, insufficient permissions, or mismatched data formats. The extracted diagnostics indicate that the core error lies in the API sync failure, with a root cause guess of insufficient technical expertise to implement the integration. The software list involved in this integration includes Make.com, Gmail, Streak, and Quickbooks.

Step-by-Step Resolution

Step 1: Configure Quickbooks API Connection

To resolve the API sync failure, start by configuring the Quickbooks API connection in Make.com. Create a new module, select Quickbooks as the app, and choose the "Get Deposits" function. Authenticate your Quickbooks account by providing the necessary credentials.

Step 2: Set Up Streak API Connection

Next, set up the Streak API connection in Make.com. Create a new module, select Streak as the app, and choose the "Create Pipeline" function. Authenticate your Streak account by providing the necessary credentials.

Step 3: Build the Integration Flow

Build the integration flow by connecting the Quickbooks and Streak modules. Use the "Get Deposits" function from Quickbooks as the trigger and the "Create Pipeline" function from Streak as the action. Map the necessary fields, such as deposit amount and customer name, to ensure seamless data transfer.

Step 4: Verify the Integration

Verify the integration by testing the flow. Make a deposit in Quickbooks and check if the corresponding pipeline is created in Streak. Ensure that the data is accurately transferred and the API sync failure is resolved.

Next Steps

To avoid the hassle of manual setup and ensure a seamless integration, we recommend deploying the flow directly using Make.com. Sign up for a Make.com account using our affiliate link: https://www.make.com/en/register?pc=shivamautomations, and take advantage of their user-friendly interface and extensive app library to automate your business processes.

Frequently Asked Questions

What is the primary cause of API sync failure between Quickbooks and Streak? The primary cause of API sync failure is often attributed to insufficient technical expertise in implementing the integration, incorrect API credentials, or insufficient permissions.
Can I use Zapier instead of Make.com for the integration? Yes, you can use Zapier as an alternative to Make.com for integrating Quickbooks and Streak. However, Make.com offers a more comprehensive and customizable solution.
How do I troubleshoot API sync failures in Make.com? To troubleshoot API sync failures in Make.com, check the module logs for error messages, verify API credentials and permissions, and ensure that the data formats match between the connected apps.

How to extract Shopify note_attributes[] values into Google Sheets columns without “Invalid array” error?

Shivam Automations — Sun, 07 Jun 2026 17:47:04 +0000

Resolving "Invalid Array" Error When Extracting Shopify note_attributes[] Values into Google Sheets

Overview

The integration of Shopify with Google Sheets is a common requirement for e-commerce businesses to streamline their operations and analytics. However, when attempting to extract specific note_attributes values from the Shopify REST API output into Google Sheets columns using Make.com (formerly Integromat), users often encounter an "Invalid array" error. This Standard Operating Procedure (SOP) aims to resolve this issue by providing a step-by-step guide on how to correctly extract and map note_attributes values into Google Sheets columns.

Error Diagnostic

The "Invalid array" error typically occurs due to incorrect usage of Make.com functions, such as map and get, when trying to extract values from the note_attributes array. This array contains nested objects, and improper handling of these nested structures can lead to errors. The root cause of the issue lies in the inability to correctly parse and access the desired values within the note_attributes array, resulting in Make.com being unable to process the data as expected.

Step-by-Step Resolution

Step 1: Configure the Shopify Module in Make.com

To begin, configure the Shopify module in Make.com to connect to your Shopify store and retrieve the necessary data. Ensure that you have the correct API credentials and permissions to access the note_attributes field.

Step 2: Parse the note_attributes Array

Use the JSON module in Make.com to parse the note_attributes array. This step is crucial in converting the array into a format that can be easily manipulated and accessed.

Step 3: Extract Specific Values Using the `Map` Function

Apply the map function to iterate through the parsed note_attributes array and extract the specific values you need. Use the get function to access the desired properties within each object.

Step 4: Create a Google Sheets Module

Set up a Google Sheets module in Make.com to create a new sheet or update an existing one with the extracted values. Ensure that you have the correct Google Sheets API credentials and permissions.

Step 5: Map Extracted Values to Google Sheets Columns

Use the map function again to map the extracted note_attributes values to the corresponding columns in your Google Sheet. Verify that the data types and formats match the requirements of your Google Sheet.

Step 6: Test and Verify the Integration

Test the integration by running the scenario and verifying that the extracted note_attributes values are correctly populated in your Google Sheet. Check for any errors or discrepancies and adjust the configuration as needed.

Next Steps

To avoid the hassle of manual setup and potential errors, consider deploying the flow directly using Make.com. By registering through our affiliate link (https://www.make.com/en/register?pc=shivamautomations), you can streamline your Shopify and Google Sheets integration, ensuring a seamless and efficient data exchange.

Frequently Asked Questions

Q: What is the cause of the "Invalid array" error when extracting note_attributes values? A: The error is typically caused by incorrect usage of Make.com functions, such as map and get, when trying to extract values from the note_attributes array.
Q: How can I parse the note_attributes array in Make.com? A: Use the JSON module in Make.com to parse the note_attributes array, converting it into a format that can be easily manipulated and accessed.
Q: Can I use Zapier instead of Make.com for this integration? A: While Zapier is a viable option, Make.com offers more advanced features and flexibility, making it a better choice for complex integrations like this one.

Best structure for daily PDF DDT generation + route briefing from Shopify/Google Sheets orders

Shivam Automations — Sun, 07 Jun 2026 17:46:40 +0000

Automating Daily PDF DDT Generation and Route Briefing from Shopify and Google Sheets Orders

Overview

The integration of Shopify, Google Sheets, and other software systems like Make.com, Twilio, and WhatsApp Cloud API is crucial for automating business processes. One common pain point for businesses is generating daily PDF DDT (Delivery Duty Paid) and route briefing from orders received through Shopify and Google Sheets. This process can be tedious and prone to errors when done manually. In this article, we will explore the best structure for automating this process.

Error Diagnostic

The core issue lies in the potential synchronization problems between data sources, PDF generation, and email attachment handling. The root cause of these issues can be attributed to the complexity of workflow structure and scheduling. Without a well-designed automation process, businesses may face difficulties in managing their orders, resulting in delayed deliveries and decreased customer satisfaction.

Step-by-Step Resolution

Step 1: Setting Up Shopify and Google Sheets Integration

Configure Make.com to connect with Shopify and Google Sheets, enabling the automation of data transfer between the two platforms. This involves creating a new scenario in Make.com, adding Shopify and Google Sheets as modules, and setting up the necessary webhooks.

Step 2: Creating a PDF Generation Module

Use Make.com's PDF generation module to create a custom PDF template for DDT and route briefing. This template should include relevant order information, such as customer name, address, and order details.

Step 3: Scheduling the Automation Workflow

Schedule the automation workflow to run daily, using Make.com's scheduling feature. This ensures that the PDF generation and route briefing process is automated and occurs at the same time every day.

Step 4: Verifying the Automation Process

Verify the automation process by testing the workflow and checking the generated PDF files for accuracy. Ensure that the PDF files are correctly attached to emails and sent to the designated recipients.

Next Steps

To avoid the hassle of manual setup, we recommend deploying the flow directly using Make.com. By registering through our affiliate link (https://www.make.com/en/register?pc=shivamautomations), you can streamline your automation process and focus on growing your business.

Frequently Asked Questions

Q: What is the best way to handle errors in the automation workflow? A: Make.com provides a built-in error handling feature that allows you to catch and handle errors in your workflow. You can also set up notifications to alert you of any errors that occur.
Q: Can I customize the PDF template to fit my business's branding? A: Yes, Make.com's PDF generation module allows you to customize the template to fit your business's branding and requirements.
Q: How do I ensure that the automation workflow is secure and compliant with data regulations? A: Make.com provides a secure and compliant platform for automating your workflows. You can also take additional measures, such as encrypting your data and using secure webhooks, to ensure the security and compliance of your automation workflow.

Parse JSON module fails on Claude Haiku HTTP output — "Source is not valid JSON" Body:

Shivam Automations — Sun, 07 Jun 2026 08:19:32 +0000

Resolving "Source is not valid JSON" Error in Claude Haiku HTTP Output for B2B Integration

Overview

The integration of Anthropic Claude Haiku API with Make.com often encounters a critical error where the Parse JSON module fails due to "Source is not valid JSON." This issue arises from the interaction between Make.com, a popular automation platform, and the Anthropic Claude Haiku API, which is used for generating human-like text based on input prompts. The pain point here is the inability to parse the JSON output from the Claude Haiku API, hindering the automation workflow.

Error Diagnostic

The error is diagnosed with the following details:

Software List: Make.com and Anthropic Claude Haiku API are involved.
Core Error: Module 94 fails to parse JSON output from Module 87 due to a DataError, specifying that the source is not valid JSON.
Root Cause Guess: The potential cause is a schema mismatch or incorrect JSON formatting in the output from the Anthropic Claude Haiku API. This suggests that the issue lies in how the JSON data is structured or formatted, making it incompatible with the expectations of the Parse JSON module in Make.com.

Step-by-Step Resolution

Step 1: Verify the JSON Output

First, directly inspect the JSON output from the Anthropic Claude Haiku API to identify any formatting issues or deviations from the expected schema. This can be done by logging the output in Make.com or using a tool like Postman to test the API call.

Step 2: Adjust the JSON Schema

If the JSON output does not match the expected schema, adjust the schema in the Parse JSON module to match the actual structure of the JSON data. This might involve adding or removing fields, or adjusting the data types of the fields.

Step 3: Use a Custom Script

If adjusting the schema does not resolve the issue, use a custom script in Make.com to preprocess the JSON output. This script can clean up the JSON, handle any inconsistencies, and ensure it conforms to the expected format before it is passed to the Parse JSON module.

Step 4: Verify the Resolution

After implementing the adjustments or the custom script, verify that the Parse JSON module can successfully parse the JSON output. This can be done by running a test scenario in Make.com and checking for any errors.

Next Steps

To avoid the hassle of manual setup and troubleshooting, consider deploying your automation workflow directly using Make.com. By registering through our affiliate link (https://www.make.com/en/register?pc=shivamautomations), you can streamline your B2B integration processes and leverage the full potential of automation without the initial setup headaches.

Frequently Asked Questions

Q: What is the common cause of the "Source is not valid JSON" error in Make.com? A: The most common cause is a mismatch between the expected JSON schema and the actual JSON output from the API or module.
Q: How can I troubleshoot JSON parsing issues in Make.com? A: Start by inspecting the JSON output directly, then adjust the schema or use a custom script to preprocess the JSON data if necessary.
Q: Can I automate the resolution of JSON parsing errors in Make.com? A: Yes, by using custom scripts or adjusting the module settings, you can automate the handling of JSON parsing errors and ensure your workflows run smoothly.

Extracting email addresses from Google Calendar

Shivam Automations — Sun, 07 Jun 2026 08:19:07 +0000

Resolving Email Address Extraction Issues from Google Calendar using Make.com

Overview

The integration of Google Calendar, Gmail, and automation platforms like Make.com is crucial for streamlined B2B operations. However, users often encounter issues when trying to extract email addresses from Google Calendar events. This Standard Operating Procedure (SOP) aims to address the common pain point of failed email address extraction due to display issues and incorrect aggregator usage, providing a clear path to resolving the core error.

Error Diagnostic

The core error lies in the failure to extract email addresses from the raw text bundle, primarily due to schema mapping issues. This could be a result of URL encoding or formatting problems that prevent the array aggregator from working correctly. The software systems involved include Make.com, Google Calendar, and Gmail, indicating a need for precise configuration and mapping to resolve the issue.

Step-by-Step Resolution

Step 1: Configure Google Calendar Module in Make.com

To begin resolving the issue, navigate to Make.com and create a new scenario. Add a Google Calendar module, selecting the "Get events" operation to fetch events from your calendar. Ensure you have the correct calendar ID and authentication set up.

Step 2: Extract Email Addresses from Event Descriptions

Next, add a "Text parser" module to extract email addresses from the event descriptions. Use a regular expression to match email address patterns. The regular expression pattern for matching most common email addresses is \b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b.

Step 3: Use Array Aggregator for Email Addresses

After extracting email addresses, use an "Array aggregator" to collect all the email addresses into a single array. This step is crucial for handling events with multiple attendees or email addresses.

Step 4: Verify the Extracted Email Addresses

To verify that the email addresses are correctly extracted and aggregated, add a "Debugger" module at the end of your scenario. Run the scenario and check the output of the debugger to ensure the email addresses are as expected.

Next Steps

Instead of manually setting up the integration, which can be time-consuming and prone to errors, consider deploying the flow directly using Make.com. By registering through our affiliate link, https://www.make.com/en/register?pc=shivamautomations, you can streamline your B2B automation processes efficiently.

Frequently Asked Questions

Q: What is the common cause of email address extraction failure from Google Calendar events? A: The common cause is schema mapping issues with the raw text bundle, possibly due to URL encoding or formatting problems.
Q: How can I ensure accurate extraction of email addresses from event descriptions? A: Use a regular expression in a text parser module to match email address patterns, and then use an array aggregator to collect all extracted addresses.
Q: What is the recommended platform for automating the extraction and integration of email addresses from Google Calendar? A: Make.com is a highly recommended platform for automating such tasks due to its ease of use, flexibility, and integration capabilities with Google services.

Make/API automation fixes and 48h MVP sprints

Shivam Automations — Sat, 06 Jun 2026 17:09:01 +0000

Resolving API Sync Failure and Broken Make Scenarios in B2B Automation

Overview

The integration of various software systems such as Make.com, Google Sheets, Airtable, Notion, CRM, OpenAI, and Claude is crucial for efficient B2B automation. However, API sync failures and broken Make scenarios can hinder the productivity of businesses, causing delays and losses. This Standard Operating Procedure (SOP) aims to provide a comprehensive guide to resolving these issues and ensuring seamless integration.

Error Diagnostic

The core error of API sync failure or broken Make scenarios can be attributed to several root causes, including:

Schema mapping issues: Incorrect or incomplete mapping of data fields between different software systems can lead to integration failures.
Missing auth scopes: Insufficient authorization scopes can restrict access to necessary data, causing API sync failures.
Rate limit issues: Exceeding the rate limits set by software systems can result in temporary or permanent integration failures.

Step-by-Step Resolution

Step 1: Identify and Verify the Error

Identify the specific error message or symptom of the API sync failure or broken Make scenario. Verify the error by checking the integration logs and monitoring the system's performance.

Step 2: Review and Update Schema Mapping

Review the schema mapping between the integrated software systems to ensure that all necessary data fields are correctly mapped. Update the schema mapping as needed to resolve any mapping issues.

Step 3: Check and Update Auth Scopes

Check the authorization scopes granted to the integrated software systems to ensure that they have the necessary access to perform the required actions. Update the auth scopes as needed to resolve any access issues.

Step 4: Configure Rate Limiting

Configure rate limiting settings to prevent exceeding the rate limits set by the software systems. This can include setting up batch processing, scheduling, or implementing exponential backoff strategies.

Step 5: Test and Verify the Integration

Test the integration by running a sample scenario or a small batch of data. Verify that the integration is working correctly and that the API sync failure or broken Make scenario has been resolved.

Next Steps

To avoid manual setup and configuration, we recommend deploying the flow directly using Make.com. Sign up for Make.com using our affiliate link: https://www.make.com/en/register?pc=shivamautomations. This will provide you with a streamlined and efficient way to integrate your software systems and resolve API sync failures and broken Make scenarios.

Frequently Asked Questions

Q: What is the most common cause of API sync failure in B2B automation? A: The most common cause of API sync failure is schema mapping issues, which can be resolved by reviewing and updating the schema mapping between the integrated software systems.
Q: How can I prevent rate limit issues in my B2B automation integration? A: You can prevent rate limit issues by configuring rate limiting settings, such as setting up batch processing, scheduling, or implementing exponential backoff strategies.
Q: What is the benefit of using Make.com for B2B automation integration? A: Make.com provides a streamlined and efficient way to integrate software systems, resolve API sync failures and broken Make scenarios, and automate business processes, resulting in increased productivity and reduced errors.

Only One Email Retrieved from Google Calendar Attendees Array

Shivam Automations — Sat, 06 Jun 2026 17:08:37 +0000

Resolving the "Only One Email Retrieved from Google Calendar Attendees Array" Error in B2B Integrations

Overview

The integration of Google Calendar with other business applications is crucial for efficient workflow management. However, users of Make.com, Google Docs, and Google Calendar often encounter an issue where only one email address is retrieved from the Google Calendar attendees array. This problem hinders the automation of tasks that rely on attendee information, causing inefficiencies in B2B operations. The software systems involved include Make.com for automation, Google Calendar for scheduling, and Google Docs for documentation.

Error Diagnostic

The core error, "Only one email address appears from Google Calendar Attendees array," suggests a potential issue with data processing or mapping in Make.com, possibly related to handling multiple attendees in the Google Calendar module. The root cause could be attributed to incorrect configuration or limitations in the integration module. Understanding the diagnostics is crucial for devising an effective resolution strategy. The extracted diagnostics provide the following insights:

Software list: Make.com, Google Docs, Google Calendar
Core error: Only one email address appears from Google Calendar Attendees array
Root cause guess: Potential issue with data processing or mapping in Make.com, possibly related to handling multiple attendees in the Google Calendar module

Step-by-Step Resolution

Step 1: Review and Adjust the Google Calendar Module Configuration

Ensure that the Google Calendar module in Make.com is correctly configured to retrieve all attendee emails. This involves checking the module settings for any limitations on the number of attendees it can handle.

Step 2: Use a Custom Script to Parse Attendee Emails

If the module itself has limitations, use a custom script within Make.com to parse the attendee emails from the Google Calendar event. This script can loop through all attendees and extract their email addresses.

Step 3: Verify the Integration with a Test Event

Create a test event in Google Calendar with multiple attendees and run the integration to verify that all attendee emails are correctly retrieved and processed by Make.com.

Step 4: Deploy the Resolved Integration

Once the integration is verified to work correctly with multiple attendees, deploy it to the production environment. Ensure that all future events are correctly processed, and all attendee emails are retrieved as expected.

Next Steps

To avoid the hassle of manual setup and potential errors, consider deploying the flow directly using Make.com. By registering through our affiliate link, https://www.make.com/en/register?pc=shivamautomations, you can streamline your B2B integrations and automate tasks efficiently, skipping the manual configuration process.

Frequently Asked Questions

Q: What causes the "Only one email retrieved" error in Google Calendar attendees array?

A: The error is typically caused by incorrect configuration or limitations in the Make.com Google Calendar module, affecting its ability to handle multiple attendees.

Q: How can I verify that my integration is working correctly?

A: Create a test event with multiple attendees in Google Calendar and run the integration. If all attendee emails are correctly retrieved and processed, the integration is working as expected.

Q: Can I use a custom script to resolve the issue if the module has limitations?

A: Yes, using a custom script within Make.com can help parse attendee emails from the Google Calendar event, overcoming module limitations and ensuring all emails are retrieved.

DEV Community: Shivam Automations

Canvas LMS 'Get a Submission' module

Resolving Canvas LMS 'Get a Submission' Module Errors: A Step-by-Step Guide

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Verify Canvas LMS API Configuration

Step 2: Validate Course ID, Assignment ID, and User ID

Step 3: Configure the Get a Submission Module

Step 4: Verify the Integration

Next Steps

Frequently Asked Questions

Simplest way to let OpenAI search an external legal API during a workflow?

Integrating OpenAI with External Legal API: A Step-by-Step Guide to Seamless Workflow Automation

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Setting Up the External Legal API Connection in Make.com

Step 2: Configuring the OpenAI Module in Make.com

Step 3: Creating a Custom Integration Using Make.com's HTTP Module

Step 4: Mapping Response Data and Verifying the Integration

Next Steps

Frequently Asked Questions

Need help with integrating Whatsapp with Make

Resolving Whatsapp Integration Issues with Make.com: A Step-by-Step Guide

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Verify Whatsapp Business API Settings

Step 2: Check API Connection and Authentication

Step 3: Configure Make.com Module

Step 4: Test and Verify the Integration

Next Steps

Frequently Asked Questions

Shopify Watch Orders only works when manually started — how to process new paid orders automatically?

Resolving Shopify Watch Orders Automation: A Step-by-Step Guide to Processing New Paid Orders Automatically

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Configure Shopify Watch Orders Trigger

Step 2: Set Up Webhook in Shopify

Step 3: Create a Scenario in Make.com

Step 4: Integrate with Google Sheets

Step 5: Verify the Setup

Next Steps

Frequently Asked Questions

Make.community Expert

B2B Integration Solution for Seamless Automation with Make.com and Zapier

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Choose an Integration Platform

Step 2: Configure Your Modules

Step 3: Map Your Data

Step 4: Test Your Scenario

Step 5: Deploy and Monitor

Next Steps

Frequently Asked Questions

Quickbooks deposit triggers Streak

Resolving Quickbooks Deposit Triggers Streak API Sync Failure

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Configure Quickbooks API Connection

Step 2: Set Up Streak API Connection

Step 3: Build the Integration Flow

Step 4: Verify the Integration

Next Steps

Frequently Asked Questions

How to extract Shopify note_attributes[] values into Google Sheets columns without “Invalid array” error?

Resolving "Invalid Array" Error When Extracting Shopify note_attributes[] Values into Google Sheets

Overview

Error Diagnostic

Step-by-Step Resolution

Step 1: Configure the Shopify Module in Make.com

Step 2: Parse the note_attributes Array

Step 3: Extract Specific Values Using the Map Function

Step 4: Create a Google Sheets Module

Step 5: Map Extracted Values to Google Sheets Columns

Step 6: Test and Verify the Integration

Step 3: Extract Specific Values Using the `Map` Function