Hello, I am new here on Make.com but the business I am in is not. First of all thanks to anyone who reads this and your thoughts and feedback is mucha appreciated. After several weeks working on scenarios within Make and Wondrai and running into error messages and spending hours trying to solve them I am reaching out for help. I maybe should have just posted this in “hire a Make developer” section but it is here until someone says get lost and hire someone. I have gotten along way and will continue to educate myself as well as share the end workflow publicly here at Make no matter how it comes to fruition. Here is what I am attempting to do and hitting roadblocks here or there (yes I used AI to generate this but it was from my workflow discussions with it and it summarizing what to do here- and I did in Wondrai but with errors and they have no customer support like here:
Print On Demand Semi-automated Workflow Process
- Monitor Google Sheets for New Entries
- Module Selection: Choose the “Google Sheets > Watch Rows” module.
- Configuration: Select your Google Sheets file and the specific sheet you’re interested in. Configure it to monitor new rows in column A, where your prompts are expected to be entered.
- Outcome: This setup will trigger the rest of your Make scenario whenever a new row is added to column A.
- Generate an Image from Text Prompt Using OpenAI
- Module Selection: Use the “OpenAI > Create Image” module, assuming this is available for generating images based on text prompts.
- Configuration: Input the text prompt from the newly added Google Sheets row into the OpenAI module. Adjust any other necessary parameters such as style, size, or model (e.g., DALL·E 2) to tailor the image generation.
- Outcome: OpenAI generates an image based on the prompt, which you can then use in subsequent steps of the workflow.
- Compress and Resize the Generated Image
Since direct image processing might not be fully supported within Make:
Workaround:
- Approach: You might need to use a cloud function (AWS Lambda, Google Cloud Functions) that you create for image processing. Alternatively, an external service with an API for image resizing and compression can be used.
- Module Selection: Utilize the “HTTP > Make a Request” module to call your cloud function or the external service’s API.
- Configuration: Send the generated image to the service/function for compression. Specify the desired output size (e.g., 100x100 pixels).
- Outcome: Receive the processed (compressed and resized) image, ready for the next steps.
- Upload the Compressed Image to Cloud Storage
Depending on your choice of cloud storage (e.g., Google Drive, Dropbox):
- Module Selection: Choose the appropriate module for your cloud storage provider, like “Google Drive > Upload a File”.
- Configuration: Configure the module with the necessary credentials and path details for where you want the image stored. Use the output from the image compression step as the file to upload.
- Outcome: The image is uploaded to your cloud storage, and you obtain a URL for the uploaded image.
- Update Google Sheets with the Image URL and Insert a Checkbox
To update the Google Sheet with the image URL:
- Module Selection: Choose “Google Sheets > Update a Row”.
- Configuration: Use this module to insert the URL of the compressed and uploaded image into the cell adjacent to the original prompt. If directly inserting a checkbox isn’t supported:
- Workaround: You may need to use a script or a custom API that Make can call to insert a checkbox into the next cell. This could involve using Google Apps Script and triggering it via a webhook or an HTTP request from Make.
- Monitor Checkbox for Approval
This process requires a bit of creativity since Make doesn’t directly monitor cell changes or does it with a module?
- Approach: Use a Google Apps Script to monitor the checkbox cell for changes and then call a Make webhook when an approval is detected. Alternatively, set up periodic checks with the “Google Sheets > Get a Cell” module to see if the checkbox has been marked.
- Configuration: Configure the webhook in Make or the periodic check to trigger the next step of your workflow when approval is confirmed.
- Upon Approval, Upload Image to Printify
With Make’s Printify module:
- Module Selection: Select the appropriate Printify module action, such as “Create a Product” or “Update a Product”.
- Configuration: Connect your Printify account if not already done. Fill in the product details, using the approved image URL. Specify the product type, size, color, and other relevant details based on your Printify product setup.
- Outcome: This action creates or updates a product in Printify with the approved image, ready for sale or further action.
- Error Handling and Notifications
- Module Selection: For each critical step in your workflow (especially those involving external APIs like OpenAI, cloud functions for image processing, and interactions with Printify), consider adding error handling logic.
- Configuration: Use the “Tools > Filter” and “Email > Send an email” modules to check for errors or unexpected responses. If an error is detected, configure the email module to send a notification to your designated address with details about the error and which step it occurred at.
- Outcome: You’ll be promptly informed about any issues in your workflow, allowing for quick intervention and resolution.
- Optimizing the Workflow
- Batch Processing: If your workflow handles a large volume of entries, investigate whether any of the services you’re using (Google Sheets, OpenAI, Printify) support batch requests. This can reduce the number of API calls and speed up the process.
- Scheduled Checks vs. Triggers: For parts of your workflow relying on periodic checks (like monitoring for approval), consider the trade-off between reaction time and API usage. More frequent checks mean quicker responses but more API calls.
- Module Optimization: Regularly review each module’s configuration to ensure it’s using the optimal settings, especially concerning API limits, data transfer sizes, and execution times.
- Scalability and Maintenance
- Scalability: Assess the capacity of each part of your workflow, especially third-party services. Understand the API rate limits and quotas, and consider upgrading your plans or optimizing usage to handle increased load.
- Maintenance: Set up a regular review schedule for your workflow. This includes checking for any updates or changes to the Make modules, third-party APIs, and ensuring your scripts or cloud functions are running efficiently.
- Documentation: Keep detailed documentation of your workflow setup, including API keys, module configurations, and custom code. This is invaluable for troubleshooting, making changes, or scaling your operations.
Thanks to each person that responds here.
