Repair Apollo.io Auth in Make
Budget: $15 – $25 USD
After updating my Apollo.io API key, every Make (Integromat) scenario that calls Apollo now throws an authentication error. I already replaced the key inside Make, yet the connection still fails.
I need someone who knows both Apollo.io’s API and Make’s HTTP/connector modules to:
• Inspect the current connection settings and pinpoint why the 401/403 response appears.
• Re-authenticate or rebuild the module as needed so a test call returns success.
• Show me the exact changes (key location, header format, or rate-limit setting) so I can repeat the fix in other scenarios.
A quick screenshare or concise step-by-step recap is fine—once the scenario runs without errors, the job is complete.
Project Summary: Apollo × Make (Integromat) Automation
Goal:
Automatically enrich all Apollo contacts with a gender-based salutation (“Herr” / “Frau”) using GenderAPI and update the result back into Apollo.
This automation should work both for new contacts and for existing ones in batch.
What has been done so far
Tools used:
Make (formerly Integromat)
Apollo.io Professional Plan (active API access)
GenderAPI.io
Current setup:
HTTP module in Make calling Apollo’s endpoint:
https://api.apollo.io/api/v1/contacts/search
Headers:
Content-Type: application/json
Authorization: Bearer <API_KEY>
Body examples tested:
{
"page": 1,
"per_page": 25,
"person_titles": ["marketing manager"],
"has_email": true
}
GenderAPI call works perfectly in Make (tested separately).
Current issue:
The Apollo “contacts/search” call keeps returning
Error: 422 Unprocessable Entity
even with valid parameters.
The same API key works for other Apollo endpoints, so the token is valid.
The goal is to make this “contacts/search” call return data so that the rest of the flow (iterator → GenderAPI → router → PATCH update) can be connected.
What is needed now
A working Make HTTP module configuration that successfully retrieves contact data from Apollo (/contacts/search or equivalent endpoint).
Confirmation of the correct endpoint and payload structure for the current Apollo Professional API.
Once data is retrieved, verify the next steps:
Iterate over contacts
Send first name to GenderAPI
Receive gender
Update Apollo via PATCH with "custom_fields": { "Anrede": "Herr/Frau" }
Priority: High – automation must run within Make ASAP for a live project.
Deliverable: Working Make scenario (or Postman example) that successfully returns contacts and can be extended for the GenderAPI + PATCH logic.
I need someone who knows both Apollo.io’s API and Make’s HTTP/connector modules to:
• Inspect the current connection settings and pinpoint why the 401/403 response appears.
• Re-authenticate or rebuild the module as needed so a test call returns success.
• Show me the exact changes (key location, header format, or rate-limit setting) so I can repeat the fix in other scenarios.
A quick screenshare or concise step-by-step recap is fine—once the scenario runs without errors, the job is complete.
Project Summary: Apollo × Make (Integromat) Automation
Goal:
Automatically enrich all Apollo contacts with a gender-based salutation (“Herr” / “Frau”) using GenderAPI and update the result back into Apollo.
This automation should work both for new contacts and for existing ones in batch.
What has been done so far
Tools used:
Make (formerly Integromat)
Apollo.io Professional Plan (active API access)
GenderAPI.io
Current setup:
HTTP module in Make calling Apollo’s endpoint:
https://api.apollo.io/api/v1/contacts/search
Headers:
Content-Type: application/json
Authorization: Bearer <API_KEY>
Body examples tested:
{
"page": 1,
"per_page": 25,
"person_titles": ["marketing manager"],
"has_email": true
}
GenderAPI call works perfectly in Make (tested separately).
Current issue:
The Apollo “contacts/search” call keeps returning
Error: 422 Unprocessable Entity
even with valid parameters.
The same API key works for other Apollo endpoints, so the token is valid.
The goal is to make this “contacts/search” call return data so that the rest of the flow (iterator → GenderAPI → router → PATCH update) can be connected.
What is needed now
A working Make HTTP module configuration that successfully retrieves contact data from Apollo (/contacts/search or equivalent endpoint).
Confirmation of the correct endpoint and payload structure for the current Apollo Professional API.
Once data is retrieved, verify the next steps:
Iterate over contacts
Send first name to GenderAPI
Receive gender
Update Apollo via PATCH with "custom_fields": { "Anrede": "Herr/Frau" }
Priority: High – automation must run within Make ASAP for a live project.
Deliverable: Working Make scenario (or Postman example) that successfully returns contacts and can be extended for the GenderAPI + PATCH logic.
Related categories:
Technical Support
Debugging
Software Development
API
HTTP
Automation
API Integration
Apollo
API Testing
Make.com