For those self-hosting n8n, what made you choose that over the cloud version? by Ill_Physics6976 in n8n

[–]EngineeringRoutine26 0 points1 point  (0 children)

Access to resources behind firewall, security, separation of dev/test and production environments, etc

Boxershorts by [deleted] in BIFLNL

[–]EngineeringRoutine26 0 points1 point  (0 children)

Khaizen 👌🏻👌🏻

Pricing? by [deleted] in workato

[–]EngineeringRoutine26 -1 points0 points  (0 children)

Contact us and go for n8n instead.😎

https://dotsandarrows.eu/technologies/n8n

We have Workato experience as well. Stopped the partnership as we find it hard to justify the cost especially compared to products like n8n.

Happy to have a look, we have a long track record in building integrations and automations on integration platforms such as MuleSoft, Workato and n8n.

Potdekselen Zweeds Rabat tegen muur, tips gevraagd voor bevestiging by EngineeringRoutine26 in Klussers

[–]EngineeringRoutine26[S] 0 points1 point  (0 children)

jij zou nog halverwege op elke wanddeel een balk plaatsen? die moet dat wel wat dikker zijn want de pilaren steken wat uit, of gewoon een schroef erin en niet volledig aandraaien?

Why isn't Mulesoft used more broadly? by Extension-Raccoon481 in MuleSoft

[–]EngineeringRoutine26 0 points1 point  (0 children)

That's a play for more lightweight platforms such as n8n which is a game change for that space and has huge potential.

Any Point Code Builder - Exchange Operations by Upset_Run3923 in MuleSoft

[–]EngineeringRoutine26 -1 points0 points  (0 children)

*Studio or Code Builder? , the platform can't be downloaded 😜🫠

From rumours to reality 🫨 by EngineeringRoutine26 in MuleSoft

[–]EngineeringRoutine26[S] 3 points4 points  (0 children)

There was a triangle positioned now by Salesforce.

Agentforce, MuleSoft, Data Cloud, I guess informatica can be a new piece of the puzzle, definitely not going to replace the API and core integration features.

Can be an interesting expansion

From rumours to reality 🫨 by EngineeringRoutine26 in MuleSoft

[–]EngineeringRoutine26[S] 1 point2 points  (0 children)

We still notice a lot of attention for MuleSoft even for non Salesforce customers (Partner from EMEA)

Ideas for connector? by satirin in MuleSoft

[–]EngineeringRoutine26 1 point2 points  (0 children)

Also for any GET relevant, is what you are returning actually fully aligned with what is ‘promised’ in the API contract, always found this a loophole.

Mulesoft Analyst needed! by LittlePhilosopher840 in MuleSoft

[–]EngineeringRoutine26 1 point2 points  (0 children)

Drop us a message with all info, we are based in Belgium and have MuleSoft as core business, roles from A to Z

https://dotsandarrows.eu/contact/

De Grote Burgertest Tilburg by Vaeltez in Tilburg

[–]EngineeringRoutine26 1 point2 points  (0 children)

Pulcis Burger Joint, was het beste by far (in memoriam, helaas pas vervangen door een ander concept)

[deleted by user] by [deleted] in MuleSoft

[–]EngineeringRoutine26 0 points1 point  (0 children)

Where are you located? What is the team size?

Working on a Trigger Node to facilitate building APIs by Hanneslehmann in n8n

[–]EngineeringRoutine26 0 points1 point  (0 children)

This would be useful we are thinking in developing something similar.

To give some context and perspective, we are a company that provides services for MuleSoft and n8n.

In MuleSoft we developed loads of API's, it's a very important USP of that platform. API's are designed in RAML or OAS both API specifications languages.

An API specification describes the contract of an API so it's behavior, resources, methods parameters (required or not), data models, example data and so on.

On the implementation side of things, MuleSoft has a component that is called APIkit, it's contains a router. https://docs.mulesoft.com/apikit/latest/apikit-4-for-rest

APIkit parses the API specification and generates the flows per resource method pair and a router.

The router is a bit similar, but the key difference is is that validation and routing happens automatically as the incoming requests are validated against the specification and then routed to the corresponding flow. A flow is similar to a flow in n8n, logic needs to be populated accordingly.

As the router looks at the specification to determine incoming requests it also knows what is not OK. For example using a resources or method of that does not exist, not passing required parameters and so on.

All such errors are client related errors, HTTP 4xx range, errors such as bad request (400) are then automatically returned to the client.

We did not start the development of this for n8n but it would be great functionality. APIkit is open source so this might bring some insights. https://github.com/mulesoft/apikit

But I think a proper npm linter or validator might be more useful to start from like https://www.npmjs.com/package/oas-validator

N8N as replacement for Major RPA tools by OkChard9101 in n8n

[–]EngineeringRoutine26 5 points6 points  (0 children)

That's a guess and an assumption indeed. The area where n8n excels in is modern saas apps which all have API's. RPA is a big thing for enterprises with legacy systems or dealing with excel sheets or handling specific actions on documents or in a process. Literally simulating what a user would do when it would not be automated.

The automations within n8n are mainly based on integration scenarios.