Home › Guides › Why doesn't my automation connect to a specific service?

Why doesn't my automation connect to a specific service?

By the Astraq editorial team · independent guide
October 13, 2026
Why doesn't my automation connect to a specific service?

Check if an integration exists

Your platform may not support the service natively. Search the platform's app library. If it's not there, you'll need to use a generic HTTP request and the service's API manually.

Verify credentials are correct

Double-check username, password, API key, or token. Services often reject access for typos. If using an API key, confirm you copied the entire string without extra spaces.

Confirm account permissions

Your account might lack permission to create API keys or access certain features. Log into the service directly and verify your account can do what you're automating. Some services require paid plans to enable API access.

Check IP whitelisting

Some services block requests from unknown IPs. They may require you to whitelist your automation platform's IP addresses. Check the service's security settings.

Test the service's API directly

Use a tool like Postman or curl to test the API outside your automation. This confirms the API works and your credentials are valid, isolating the problem to your platform's integration.

Review error messages

Read the exact error your workflow reports. "Authentication failed" means credentials. "Rate limited" means you hit usage caps. "Endpoint not found" means the API path is wrong.

If stuck, contact the service's support with your error message and account details.

Reader reviews

Write a review

← All guides