moabuaboud

We, at https://github.com/activepieces/activepieces, had been using Depot.

Before depot we faced extreme slow builds for ARM-based images on github machines. However, using Depot helped us reduce the image build time from 2 hours (with an emulator) to just 3 minutes.

Emulator: https://github.com/activepieces/activepieces/actions/runs/39...,

Depot: https://github.com/activepieces/activepieces/actions/runs/40....

AirTable is on the way, You can see the progress of the community here: https://github.com/orgs/activepieces/projects/5

Please open an issue for Xano with your exact use case, so we know what triggers / actions you need.

https://github.com/activepieces/activepieces/issues/new/choo...

That's an innovative idea, I like it! Was it straightforward to set up automated notifications for the other services? Did you encounter any challenges or problems along the way?

Thank you for your feedback. We will improve our HTTP request in response to your query.

Our preferred method for setting up local development is through the use of a VSCode dev container, which can be found at https://www.activepieces.com/docs/contributing/local-develop....

Currently, we have not documented our use of docker-compose.dev as we are still testing it for compatibility with various systems, such as ARM-based machines like the M1 MacBook, which have encountered issues with docker-compose.dev.

However, if you prefer using docker-compose.dev over VSCode dev containers, you can run npm ci followed by running docker-compose.dev.

I hope you have a smooth experience with activepieces. If you encounter any issues, our team is available and responsive on Discord.

Our framework streamlines the process by making pieces simple to define. You only need to specify the properties and the function to carry out the action. The core takes care of everything else, from authentication to the user interface.

For further information, check out the Quickstart tutorial at https://www.activepieces.com/docs/contributing/building-piec..., or the reference guide at https://www.activepieces.com/docs/contributing/building-piec....

We have already received contributions from external contributors in the form of 6+ connectors and we take this seriously and consider them to be just as important as our workflow builder users. Hence, your feedback is highly prized and greatly appreciated.

I am delighted that you noticed the piece framework design.

The connectors have no dependency on the core. We are currently working on releasing each connector as a separate npm package, which can be utilized in any codebase.

If this is useful for your particular needs, or if you have any suggestions/ questions, please let me know.

If you are interested join our discord, we do the announcements there.

Are there any programmatic methods to detect integration breakages? Simply relying on unit/integration testing with mock endpoint is not effective, as it cannot capture changes made by third parties. Being notified of breakages is a solution, but not the most ideal one.

I've considered sourcing open API specs, like APIsguru.com, to scan for changes, but I was wondering if you have any other suggestions.

Yup,take look there https://activepieces.com/docs/contributing/repo-structure

Most current documentation is about the pieces package (Building Pieces Section), the rest will follow soon.

That's a decent feature. The main reasons we know of are versioning and IDE experience.

We were designed API-first. They are clean, but undocumented yet. We currently have a draft PR that generates an OpenAPI specification.

I think the next step for us would be a CLI to bring the code experience into the IDE.

What are your reasons?

The development began two months ago and we have not encountered any scaling issues yet, as the majority of users self-host. Therefore, our priority was focused on building apps. Is there anything you believe we should consider?

You are correct, repeating the same index twice is a mistake. Thanks for hinting at that

We are using nano id (https://www.npmjs.com/package/nanoid) for all entities, It's stored as varchar in the database.

Hey HN, I'm one of the co-founders of Activepieces and I just wanted to give a shoutout to everyone who's been showing us love on GitHub by giving us stars.

To show my appreciation, I created a flow using Activepieces to thank everyone on our Discord.

Screenshot: https://imgur.com/a/W5p60le

Congratulations on launch

Hi, I thought I was alone in facing this problem.

I am working on an open source project to handle all third-party integrations pain, (OAuth2 including multi tenancy, Caching, Cors, Logging, Error Rates, Rate Limting).

Basically It will be dashboard where you can trace all logs, and SDK on frontend or backend to proxy the requests through it.

The next steps to work on tooling to mock APIs and test them.

This effort still in progress and will go out during next two weeks, the repository is incomplete. https://github.com/passr-dev/passr

Do you mind if i contact you to learn more from you and shape the project together? We have discord channel https://discord.gg/xaDV2Tuh4d

Hey HN, Many of SaaS (user on-boarding /chatbots) today produce data such as tracking events, generating leads and the customers keep requesting these data to be sent to their warehouses / CRMs / Analytics.

Instead of building all the destinations (CRM & Analytics integrations) in-house, You could use Link from activepieces to offer 1-click integrations for your customers inside your web application.

Let me know what you guys think of the idea and if you see any potential pitfalls.

Interesting, I was thinking of a way to support many CRMs integrations without building all of them in-house