navaneethpk

A customer of ours at ToolJet, specializing in service-based offerings, traditionally used Tableau for their analytics needs. They decided to give us a shot and started moving some of their customers over to ToolJet, taking advantage of our Plotly-based chart component for visualizations. While the initial lift to replicate their Tableau setups in ToolJet is non-trivial, the value proposition is turning out to be significantly more compelling. They're now confidently migrating more customers.

They're aware that our platform might hit some snags with the more complex use cases but most of their customers have similar use cases that are less complex.

Right! Getting September 2021 as the answer if accessing from India & January 2022 if I use VPN (US)

I'm using the paid version.

"The knowledge cut-off date for my training data is up until September 2021. However, I can access real-time information via my browsing tool. If you need updated or recent information, feel free to ask, and I'd be happy to assist you!"

Getting the same old response still.

It is a generic connector for OAuth. Since Xero supports OAuth 2.0, it should be a similar process to integrate. Feel free to ping us [hello@tooljet.com] if you run in to any issues.

Yes, that should be easy. Here is the guide for using OAuth - https://docs.tooljet.com/docs/how-to/oauth2-authorization/.

Thank you. Will fix it asap.

Heroku removed their free tier.

Thanks. The issue is now fixed.

Yes, makes sense. We will remove this asap.

ToolJet is open-source - https://github.com/ToolJet/ToolJet

Hey HN,

Founder here, I’m excited to announce that we've just launched the beta version of ToolJet’s Workflow Automation tool!

For those unfamiliar, ToolJet started its journey when we open-sourced ToolJet (https://github.com/ToolJet/ToolJet) here on HackerNews back in June 2021 (https://news.ycombinator.com/item?id=27421408). When we launched ToolJet, we aimed to bridge the gap between developers and non-developers, making it easier for teams to build internal tools swiftly. Our journey began right here on HackerNews, and much of our evolution has been shaped by feedback from many of you. Today, we’re taking a step further with our new Workflow Automation tool.

How it works

1. Connect your data sources: Add any of the pre-existing ~50 data sources like PGSQL, RestAPI, Zendesk, Stripe, Amazon S3 and many more.

2. Create a workflow: Create a new workflow from your ToolJet Dashboard. A workflow is a series of steps which are executed one after the other, and each step is interacting with a datasource by fetching or putting back data.

3. Business logic: Implement your business logic by creating branches based on conditions and by running JavaScript codes.

4. Debugging: You can see the logs by expanding logs panel at the bottom of the workflow builder. It will have all information you need to debug your workflow.

Documentation: https://docs.tooljet.com/docs/workflows/overview?ref=blog.to...

Availability

Currently, the Workflow Automation beta is available for on self-hosted instances running Business and Enterprise editions.

PS: We haven't open-sourced Workflows.

Not yet, this is not in our immediate roadmap.

Right, we are exploring this as well but don't have a solid plan yet. Since the pricing is custom, we try to provide a plan that works for a specific customer.

Thanks for reporting, fixing this asap.

Contributors have to agree to a contributor license agreement (CLA) when they create their first PR.

We've written about this choice on our blog in detail: https://blog.tooljet.com/changing-license-to-agpl/.

We are working on this actively. npm packages and Python packages from Micropip will be supported soon.

Organising queries: yes, this is also on our roadmap but yet to prioritise. Thanks for the detailed feedback.

The differences are listed out here: https://www.tooljet.com/pricing. Cloud deployment are usually a few days delayed, features are very similar.

Sorry, looks like a mistake. What free tier misses is only the granular access control. Fixing it asap.

You can create user groups and give permissions to specific apps. Permissions are either "view" or "edit". If given "view" permission, the user will not be able to make changes to the application.

Reddit has given us a lot of users. Especially r/selfhosted.

Hi HN,

Founder here, ToolJet’s story began when I launched beta version of ToolJet in June 2021 on HackerNews ([https://news.ycombinator.com/item?id=27421408](https://news....). It was very overwhelming to see the repository getting more than a thousand GitHub stars within less than 8 hours of launch. Since then we’ve grown into 16,000 stars and 300 contributors on GitHub. 1000s of teams are now using ToolJet to build and maintain their internal tools.

Today, we are excited to launch ToolJet 2.0.

We believe that any piece of software that has access to sensitive data of companies/people should be open-source and hosted on premises. Along with a strong focus on data privacy, we’ve also made sure that ToolJet as a platform is extremely flexible.

What is ToolJet?

ToolJet is an *open-source low-code framework* to build and deploy internal tools quickly. Those who already understands the low-code landscape, ToolJet is an open-source alternative to Microsoft Power Apps and Retool. ToolJet has integrations with data sources, such as databases (like PostgreSQL, MongoDB, MS SQL Server, SnowFlake, etc), API endpoints (with support for OAuth2 authorization), external services ( Airtable, Stripe, Slack, Google Sheets, Notion, etc) and even cloud storage services ( S3, GCS, Minio ).

What’s new?

- Redesigned every screen with a heavy focus on user experience. - Added in-built no-code database. This feature is built on top of PostgreSQL so that the self-hosted users can take advantage of capabilities of SQL as well. - Support for multi-page applications. - Realtime multiplayer editing so that changes from one user will not override the changes from another user. - Support for using Python ( along with already supported JavaScript ). You can use Python even for interacting with UI components. - Every installation of ToolJet can now have multiple workspaces. Each workspace can have their own SSO config and users. - ToolJet now has more than 50 data source integrations. You can also build custom connectors for ToolJet using our Plugin Development Kit ( [https://www.npmjs.com/package/@tooljet/cli](https://www.npmj... ). - We added a bunch of new UI components. Even complicated ones like Calendar and Kanban board. You can also import your own React components and use them within ToolJet apps. - ToolJet is now available in 8 languages including Spanish, Italian, German, French & Russian. - More test coverage using Cypress. We now have dedicated team members for improving test coverage.

We are still very early in our journey and there is a lot more to build. Constant feedback from the open-source community is the reason why we are here, any feedback is appreciated and happy to answer any questions.

Congrats on the launch! What is the reason behind choosing Perl?

PS: We are building https://github.com/ToolJet/ToolJet/ - built using JavaSript/TypeScript.

This is not true as I can confirm that none of ToolJet’s team members including myself do not have ability to downvote on HN. Looks like it requires certain karma threshold.

Exactly the reason why I wrote the article in a way that it just walks through the journey. The outcome of anything is a function of the context & timing and hence whatever worked for someone at a specific point of time to get to a specific stage might not be relevant for everyone.

Thanks for noticing, fixing in some time.

I might be wrong here but "Founder" is just a title and it has nothing to do with law or investors. Adding another "Director"/"Officer" requires some paperwork though.

> having a social circle to intro investors

> with negligible traction

Disagreeing to these two points. The traction from HN & ProductHunt launch was good that ToolJet got 1000+ stars on GitHub in under 8 hours. The intros were made mostly by great open-source founders who were totally strangers at the time who discovered the project mostly from HN.

The part where I begged for funding is another story: https://blog.tooljet.com/raising-vc-funding-for-open-source-...

Also the link to HN launch that helped a lot: https://news.ycombinator.com/item?id=27421408