Muda Paisagens
AI pre-sales conversations, qualification questions and records in Pipefy, integrated through Make.
See the Muda Paisagens caseIntegrations and automations to connect your operation.
EDevsHub builds integrations and automations to move information between systems, organize customer service steps and run defined routines. Before automating, we need to agree on the trigger, the rule, the destination and what happens when something fails.
- Technical lead: Eduardo Gouveia, Senior Full Stack Developer
- Workana HERO
- 187 completed projects
- Profile checked on 29/10/2026
When the problem is the handoff from one tool to another.
- A form or service channel receives data, but someone has to enter each record into the CRM.
- The team checks different systems to find out whether a step was completed.
- An already automated flow needs to handle failures, duplicates or new business rules.
Automate the rule without hiding the exceptions.
A flow must also work when the input is incomplete or a service is unavailable. During alignment, we define which situations can proceed automatically and which should stop for human review. AI can take part when the task requires interpretation; deterministic rules still make sense for validations and records.
A flow can be described from end to end.
These are examples of deliverables and acceptance criteria. The proposal defines which ones go into your project and how they will be checked.
Input and validation
Receive an event from a tool and check the fields required for the next step.
Acceptance example: Complete inputs move through the flow; records missing required fields get the agreed routing.
Record at the destination
Map the source fields to the fields of a CRM, database or other application.
Acceptance example: A test event creates or updates the correct record. The same event repeated does not create an improper duplicate.
Failure and retry
Agree on how the operation identifies a failed attempt and when it can be retried.
Acceptance example: A simulated failure is recorded; the agreed handling allows processing to resume without losing its state.
Handoff to a person
In customer service or AI interpretation flows, define the points where the team takes over.
Acceptance example: The selected handoff scenario gives the team the agreed context and stops the planned automatic actions.
From the portfolio
A related solution.
How the work is organized.
Design the flow
Describe the initial event, the data that moves, the rules and the expected result in each tool.
Check access
Validate APIs, permissions, documentation and available environments, as well as the limits of the services involved.
Implement and test
Check the expected path and the agreed exceptions, such as a duplicate event or an unavailable destination.
Prepare the operation
Document how to monitor the flow, identify a failure and carry out the planned maintenance actions.
Before defining the project.
Can every tool be integrated?
Feasibility depends on the access each product offers: API, exports, events or other authorized means. Those options are checked before the scope is confirmed. A tool without adequate access may require another solution.
Does EDevsHub use Make, n8n or code?
The choice depends on the flow, the available integrations and the expected maintenance. The Muda Paisagens case uses Make with Pipefy. A project can use an integration platform, code or a combination of both, as needed.
Does the automation need artificial intelligence?
No. When the rules are clear, a conventional integration can solve it. AI is considered when there is an interpretation, classification or customer service task that justifies it and can be evaluated with examples.
How are service accounts and costs handled?
The accounts, permissions and services required are identified when the scope is defined. Provider charges and external dependencies should be separated from development in the proposal. The amounts depend on the tools and usage.
Which information still has to be passed on by hand?
Prefer to hire through Workana? See the profile. If the conversation already started on Workana, send the context in the same chat.
To start the conversation, it helps to gather:
- The source and destination tools.
- An example of the event and the data that needs to move.
- What should happen when there is an error and who follows the routine.