This topic was automatically generated from Slack. You can find the original thread here.
Other than VPCs, what’s another way I can access an API that blocks unknown IP addresses?
If you need to access an API that blocks unknown IP addresses, but don’t want to use a Pipedream VPC, there is one alternative if you don’t need to access the HTTP response data: - You can use $send.http() to send HTTP requests from a limited set of static IP addresses. This allows you to whitelist a small, known set of Pipedream IPs on the API side. Important limitations: - This method is only suitable if you do not need to process the response from the API, since $send.http() is designed for sending data out (like webhooks or notifications), not for receiving and using the response in your workflow. If you need to receive and process the API response, using a Pipedream VPC is the recommended solution, as it provides a static, dedicated IP address for your workspace’s outbound requests. For more details, see: - Pipedream docs: Node.js code — IP addresses for HTTP requests - Pipedream docs: HTTP destinations and static IPs Let me know if you need help with a specific use case!
Using VPCs is not an option for us at the moment, and we need to receive and process data from an API, are there any other workarounds?
We are trying to integrate/use Paycom in a workflow
Since using VPCs is not an option for you right now, and you need to receive and process data from an API (like Paycom) that blocks unknown IP addresses, your options on Pipedream are limited: ### 1. Static IPs via $send.http() (with limitations) - Pipedream offers a set of static IPs for outbound HTTP requests only when using the $send.http() method. - Limitation: You cannot process the HTTP response in your workflow using this method. It’s only for sending data out (like webhooks), not for receiving and acting on the response. ### 2. No built-in static IP for standard HTTP requests - Standard HTTP requests (using axios in code steps or prebuilt actions) are sent from dynamic IP addresses, which cannot be whitelisted by Paycom. ### 3. Workarounds (with caveats) - Proxy server: You could set up your own proxy server with a static IP, whitelist that IP with Paycom, and have your Pipedream workflow send requests through the proxy. This adds complexity and cost. - Third-party integration platforms: Some platforms offer static outbound IPs by default, but this would mean moving your workflow off Pipedream. - Ask Paycom for alternatives: Some APIs allow for authentication using OAuth or API keys without IP whitelisting, or may offer a sandbox environment with relaxed IP restrictions. ### 4. Request a Pipedream integration or feature - If you need a native Paycom integration or static IP support for your use case, you can request a new integration or feature from Pipedream. — Summary: Without a VPC, you cannot reliably receive and process data from an API that requires IP whitelisting on Pipedream, unless you use a proxy or the limited $send.http() method (which doesn’t let you process responses). If you need to process API responses, a VPC or external proxy is required. If you have further questions or need help with a proxy setup, let me know! If you need more support, please visit Support - Pipedream.
are there a range of IP addresses I can give to Paycom to whitelist?
Based on the Pipedream documentation: - HTTP requests made from standard Pipedream workflows do NOT come from a fixed range of IP addresses. By default, these requests can come from a large, dynamic range of IPs. - To get a static IP (or range) for outbound HTTP requests from workflows, you must use a Pipedream VPC. - The only exception: If you use $.send.http() in your workflow, your requests will come from a documented set of static IP addresses. However, this method is limited: you cannot process the HTTP response in your workflow. Summary: - There is NOT a static IP range you can provide to Paycom for standard HTTP requests from Pipedream workflows, unless you use a VPC. - If you only need to send requests (and don’t need to process the response), you can use $.send.http() and whitelist the static IPs listed in the Pipedream documentation. - For full API integration (sending and receiving data), a VPC is required. If you need more help or want to discuss your use case, please visit Support - Pipedream.
Are you calling that API via Pipedream Connect or from the builder / String?
Is there a reason a VPC won’t work?
just budget for our project.
Got it
unless VPC can be an add-on to our plan. We only have a couple of workflows needed and will barely scratch 1500 credits/month
I think we do offer VPCs as an add-on — if you hit the Contact Sales button here on our pricing page, you can get connected with our Sales team: Pricing - Pipedream
Yes, we offer VPCs as an add-on at $100 / month.
You can reach out via the Contact Sales form as Danny mentioned above, or open a support ticket.