CreaScale + Make Integration

Prerequisites

CreaScale account with API key (generated from Settings → API).
Make account (Free tier: 1000 operations / month).
A trigger source — Shopify store, Airtable base, Google Sheet, webhook endpoint, etc.
Basic familiarity with Make's visual scenario editor (or follow screenshots below).

Step-by-step setup

Generate CreaScale API key

In CreaScale, Settings → API → Generate new key. Copy it to your Make vault for secure reuse across scenarios.

Create a new Make scenario

In Make, click "Create a new scenario". The visual editor opens. Double-click the center to add the first module.

Add your trigger module

Select your source — Shopify "Watch Products", Airtable "Watch Records", Google Sheets "Watch Rows", etc. Connect the account and configure filters. Run once to verify the trigger fires.

Add the HTTP module

Click "+" to add another module. Search "HTTP" and select "Make a request". This is the generic REST call module — it works with any API including CreaScale.

Configure the POST request

Fill the HTTP module:

URL: https://api.creascale.ai/v1/runs
Method: POST
Headers:
  - Authorization: Bearer YOUR_API_KEY
  - Content-Type: application/json
Body type: Raw
Content type: JSON (application/json)
Request content:
{
  "product_url": "{{1.product.url}}",
  "languages": ["en", "fr", "es", "ar"],
  "angle_count": 8
}
Parse response: Yes

Add a Sleep module

Add a "Tools" → "Sleep" module set to 360 seconds (6 minutes). This pauses the scenario while CreaScale processes the run.

Add second HTTP module to fetch results

Add another HTTP module, GET method. URL: https://api.creascale.ai/v1/runs/{{2.data.run_id}}. Same Authorization header. Response parsing on. This fetches the completed run data.

Add an Iterator for the creatives array

Add "Flow Control" → "Iterator". Source array: {{5.data.creatives[]}}. This loops over each of the 8 creative URLs individually so downstream modules act per-creative.

Route to final destinations

After the Iterator, add modules for your outputs — Slack "Create a Message" per creative, Google Drive "Upload a File" to download each image, Airtable "Create Record" to log the run. Multiple output paths can run in parallel after the Iterator.

Add Error Handler

Right-click the CreaScale HTTP module → "Add Error Handler" → "Break" or "Rollback". This tells Make how to handle failed runs (e.g., retry with exponential backoff, or log to an error Airtable).

Schedule and activate

Set the scenario to run on the trigger's natural cadence (e.g., "On Demand" for Shopify webhooks, "Every 15 minutes" for polling sources). Click the toggle to activate.

Popular use cases

Batch daily Shopify sync — Run at 7am daily: fetch all new Shopify products from the last 24h, iterate through them, call CreaScale for each, aggregate results into a daily Slack digest.
Conditional angle generation — If product price > $200, request 12 angles instead of 8 (higher-consideration purchase). If product category = "electronics", add technical-spec angle emphasis. Make's Router module handles this cleanly.
Multi-language parallel runs — For an international brand: iterate through target languages, call CreaScale with language-specific brand voice for each. Output aggregated in a per-language Google Drive folder.
Agency client routing — Agencies: one Make scenario, client-specific API keys fetched from a Data Store based on the trigger source. Clean segregation without duplicating scenarios.
Smart retry on fatigue — Poll Meta Ads Reporting API every 4 hours. When any ad's frequency exceeds 3.8x, trigger a fresh CreaScale run on that product's URL. Automatic fatigue refresh pipeline.

Troubleshooting

HTTP 401 on POST — Authorization header must be exactly "Bearer YOUR_KEY". Make treats whitespace literally — no extra spaces before or after.
Response parsing fails — In the HTTP module, set "Parse response" to Yes. This tells Make to parse the JSON so you can reference fields like {{data.run_id}} downstream.
Sleep module skipped — Make's Free tier has a 40-second max per-module runtime; Sleep over 300s requires Core or Pro. Upgrade or split into multiple Sleep modules.
Iterator produces empty output — The array reference path must match the API response exactly. Inspect the GET response JSON first, then adjust the Iterator source accordingly (e.g., data.creatives[] vs result.creatives[]).
Scenario consumes too many operations — Each module run = 1 operation. A complete CreaScale workflow uses ~12 operations (trigger + 2 HTTP + Sleep + Iterator + 8 downstream actions). At 100 runs/month, you need the $10.59/mo Core tier.

Frequently asked questions

Make vs Zapier — which is better for CreaScale?

Make for complex logic (branching, error handling, batching). Zapier for simple trigger→action flows. Most agencies prefer Make; most solo founders prefer Zapier. Both use CreaScale's REST API identically.

Can Make handle CreaScale's async run pattern?

Yes — using the Sleep + GET pattern shown above. CreaScale runs complete in ~5 minutes; Sleep 360s + GET works cleanly. For stricter timing, use a Webhook Listener module on CreaScale's completion webhook.

Does CreaScale plan to build a native Make app?

Yes — roadmap Q3 2026 alongside the Zapier native app. Until then, the generic HTTP module works for 100% of use cases.

Can I use Make's Data Store for caching?

Absolutely. Store run_id → output URLs mappings in a Data Store to avoid re-running CreaScale for recently-processed products. Saves credits per dedup.

How do I handle CreaScale webhook callbacks instead of polling?

Add a "Custom Webhooks" trigger in Make — Make gives you a unique URL. Pass that URL to CreaScale as the <code>callback_url</code> field in your POST body. CreaScale will POST to the Make webhook when the run completes; no Sleep+GET needed.

Connect CreaScale to Make (Integromat) — Visual Automation