Build and run API Automations in minutes

Sameera Vanekar
4 replies
Hey PHers! Looking for feedback here :) I wanted to create a workflow automation platform that ran purely on API calls. The premise is simple – 1. Add as many API calls you want 2. use the output from the previous call, into any of the subsequent calls 3. add dynamic fields to the api call inputs 4. link them all together into a workflow The workflow platform would have all the basic functionalities like looping data, conditions, multiple trigger options with a clean and simple approach to workflow building. After a year of tinkering and working with clients, we are ready to let early adopters in - Pathfix Automation If you are open to try/test out the API based system, join the waitlist and add ‘PH’ in the comments. We will push you up on the list and I will personally reach out to you and get your thought :)

Replies

Founder of Tetriz.io
That sounds interesting. How would you differ from Zapier? Will you support virtual APIs based on webscraping like Apify
Co-Founder at Pathfix
Thanks @fabian_maume The simplest differentiator is that Zapier is primarily built for end users of products (I want to connect my app 1 to my app 2). Pathfix Workflow is for product builders (nocode builders and tech) who are looking to automate their stack (internal) or add integrations to offer their users the ability to connect to their apps. You can built ANY workflow by linking ANY APIs together :) Would love to understand a bit more in the virtual APIs question - are you referring to 'Actors'?
Share
Founder of Tetriz.io
@sameeravanekar Virtual API is the idea to use webscraping to archive the same type of result than an API. It is mainly useful for website which do not offer official APIs. It is the concept behind Apify & Phantombuster Main drawback of virtual API is the latency time, as you need time to run the webscraping logic. So if you want to integrate them you need to be flexible with max API response time.
Share
Co-Founder at Pathfix
@fabian_maume that's definitely interesting! Thanks for that. As for supporting virtual APIs, yes we will support them. We will be offering to run processes asynchronously, so latency times should not be an issue.
Share