Overview
If GiveMe5 does not offer a native integration for a tool you use, Make is a way to connect that system and automate review acquisition—for example by syncing data from your stack into GiveMe5 or triggering review outreach via scenarios you build.
Make (formerly Integromat) is a hosted automation platform.
From here you can:
Copy your GiveMe5 access key — from step 1 when API access is active
Download blueprints — one file per automation pattern GiveMe5 lists
Import scenarios into Make — visual editor with modules for hundreds of apps
Run scheduled or instant automations — according to how you configure each scenario
Before you connect
Requirement | Why it matters |
Admin access in GiveMe5 | Opens Integrations and reveals API material |
API access on your GiveMe5 contract | Without it, keys stay hidden and a warning appears |
A Make team or organization that allows imports | You need permission to add new scenarios |
Safe handling of the access key | Treat it like a password |
How to set up Make with GiveMe5
Step 1: Open Integrations
Sign in as an Admin.
Open Setup → Integrations.
Step 2: Open Make
Click Make in the grid.
Read the introduction paragraph on the detail page.
Step 3: Copy your access key
When API access is enabled, complete step 1 on the page—reveal and copy the key.
If you see a no API access warning, stop here and ask your GiveMe5 account owner to enable keys.
Step 4: Download blueprints
Download each blueprint JSON GiveMe5 offers (reviews, reply, invitation, test, etc.).
Keep filenames meaningful so imports are not confused later.
Step 5: Import into Make
In Make, use Import blueprint (or the current import path for your workspace).
Open modules that call GiveMe5 and map the HTTP/Bearer credential to your copied key exactly as the blueprint expects.
Step 6: Activate and test
Run Make’s test run for the scenario.
Enable scheduling only after output matches expectations (no duplicate invitations, correct customer targets).
Step 7: Coordinate with Automation (optional)
If Make will send invitations, confirm GiveMe5 Automation is not already sending the same event—pick one orchestration path per business rule.
After you connect
Watch Make operations so scheduled runs stay inside your vendor plan.
Duplicate scenarios before risky edits so you always have a rollback copy.
Rotate keys in GiveMe5 if compromised; update Make connections the same day.
Frequently asked questions
How is Make different from n8n here?
Both rely on GiveMe5 keys + downloaded JSON; Make runs on Make’s cloud, while n8n may be self-hosted. Pick based on pricing and ops comfort.
Why no API key on the page?
API access is not on your subscription yet—contact GiveMe5 support or your owner.