Hey! 👋 That’s a common hiccup when using Influencers Club’s “Enrich influencer details” inside Clay — especially if you’re running several rows in parallel. The Gateway Timeout (504) usually means Clay’s request to Influencers Club is expiring before their API returns all results. A few fixes that usually help:
Batch smaller: Run 5–10 rows at a time instead of dozens. Influencers Club’s API can be slow for larger data pulls.
Add delays: You can use Clay’s “Run Step After Delay” or stagger runs manually to avoid rate-limit overloads.
Retry logic: If you see partial failures, right-click the errored rows and select “Retry failed rows.”
Check Influencers Club status: Sometimes their API queues requests; if it’s slow, retries after 10–15 mins usually resolve it.
If you’re planning to run large volumes (hundreds+), it’s best to contact Influencers Club support to ask about your API rate limit — Clay can only process as fast as their backend allows.
