Our Make.com bill keeps growing. What can be done?
Two things. First, scenarios can usually be restructured to do the same work for far fewer operations — loops over records are the common culprit. Second, past a certain volume, self-hosted automation removes per-operation cost entirely. We will work out where your volume actually sits before recommending either.
Should we use Make.com or self-host n8n?
Make.com if volumes are modest, you want it working this week, and you would rather not own infrastructure. Self-hosted n8n if volumes are high, or the data in those workflows is sensitive enough that you want it on your own servers. We build both, so the answer you get is not driven by what we would prefer to sell.
Can you connect a service Make.com has no module for?
Yes, through generic HTTP calls with proper authentication. It is routine, though it does mean the scenario carries more of the logic itself, which makes error handling matter more.
Why do our scenarios keep breaking?
Most often the error handling was never added — the platform makes the happy path so easy that it is a natural thing to leave for later — or a connection expired with nothing set up to raise the alarm. Both are straightforward to fix, and an audit will tell you which you are dealing with.
Can you migrate our existing scenarios somewhere else?
Yes. Scenarios are not portable, so this is a rebuild rather than an export — which is the moment to add the error handling and monitoring the originals never had.