---
title: "Make | Skills We Assign For | Azendo"
description: "Make for multi-step cloud automation — branching, error routes and the Azendo roles assigned for automation work."
url: "https://azendo.co/skills/make/"
---

[Skills](https://azendo.co/skills/) Automation platforms 

# Make.

Make is a hosted automation platform with a visual scenario builder, connecting cloud applications through multi-step workflows with branching, error handling and data transformation between steps.

## Where Make fits on a long engagement.

Make handles shape better than most of its competitors. Where a workflow needs to iterate over a list, branch on a condition or restructure a payload between two systems that disagree, the visual model expresses that without dropping to code.

Complex scenarios need the same treatment as software. Error routes, naming, and a note on the scenario explaining why it exists are what separate an automation someone can maintain next year from one that will be rebuilt because nobody dares change it.

## What an assigned team does with Make.

Automation accumulates in exactly the way documentation does not. Two years on there are forty scenarios, several business-critical, and the person who built them has moved on — which turns a small change into a week of tracing.

Keeping them maintainable is ongoing work rather than a build phase, and where the workflows touch customer-facing systems it is usually assigned alongside [outsource software development services](https://azendo.co/services/software-development/).

## What we use Make for.

* Multi-step process across several tools A sequence spanning CRM, finance and communication systems that would otherwise be manual.
* Failure handling that notifies someone Error routes so a broken run surfaces rather than silently stopping.
* Making an inherited scenario maintainable Documenting and restructuring automation that works but nobody understands.

## How Make capacity is assigned.

Assigned under [AI automation engineering](https://azendo.co/services/ai-automation-engineering/). Where a workflow has grown past what the platform handles well, we will say so rather than keep extending it.

## Roles we assign Make for

* [AI Automation Engineer AI automation engineering](https://azendo.co/services/ai-automation-engineering/ai-automation-engineer/)
* [Workflow Automation Specialist AI automation engineering](https://azendo.co/services/ai-automation-engineering/workflow-automation-specialist/)

## Service lines it sits in

* [AI automation engineering](https://azendo.co/services/ai-automation-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in automation platforms

* [n8n — skill we assign for](https://azendo.co/skills/n8n/)
* [Zapier — skill we assign for](https://azendo.co/skills/zapier/)
* [Power Automate — skill we assign for](https://azendo.co/skills/power-automate/)
* [UiPath — skill we assign for](https://azendo.co/skills/uipath/)
* [Automation Anywhere — skill we assign for](https://azendo.co/skills/automation-anywhere/)
* [Blue Prism — skill we assign for](https://azendo.co/skills/blue-prism/)
* [Workato — skill we assign for](https://azendo.co/skills/workato/)
* [MuleSoft — skill we assign for](https://azendo.co/skills/mulesoft/)

## Tell us what your roadmap needs Make for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)