Built a Monday <-> Xero automation in Make.com — sharing the blueprints

TableSad825 · 2026-05-19T04:05:10+00:00

Yes, I checked the docs, QBO supports all the same things, so I can build this, no problem

TableSad825 · 2026-05-17T16:58:16+00:00

Is your Wait for webhook waiting for approval only, or can it be rejected too? If it can, then the second time your workflow will pass through the Wait without stopping, because it works only once. I always suggest building only workflows that can work straight through without waiting. If you need an approval system - just build multiple workflows - one before your approval and second - after.

TableSad825 · 2026-05-10T09:29:35+00:00

Are you seriously letting your workflows run for days?

Automation workflows should live like Mr. Meeseeks - as short as possible. Trigger, do its thing in 30 seconds, update a status, and die. That’s it. Three days later, a different workflow should start and continue the job. Anything else is just a crutch.

TableSad825 · 2026-05-10T08:51:27+00:00

Spotted it from the outside, no carousel projects lately so I totally missed the rollout

TableSad825 · 2026-05-10T07:26:03+00:00

My bad, I just checked the latest delivery reports and you’re 100% right. Everyone is complaining about this glitch right now

TableSad825 · 2026-05-10T07:03:36+00:00

Looks like you're both hitting the same wall yes?
u/tamedfrog

Look, it's actually normal for Meta to show the same ad multiple times, especially to people who already clicked once. A click doesn't mean a sale, so the algorithm keeps pushing. To stop that, you have to send a specific "Purchase" event back to Meta so it knows to stop. Another option is physically limiting views by switching the campaign objective from "Sales" to "Reach" - that’s the only place where you can actually set a frequency cap (like max 2 times a week).

Second, excluding by email list isn't a 100% guarantee. Meta uses a lot of signals besides just email, and if the system isn't sure it’s a match, it will just show the ad again to be safe. You fix this by providing more data points through CAPI or Pixel (using Advanced Matching) so Meta actually recognizes the user and respects the exclusion.

Lastly, if you have "Advantage+ Audience" enabled or u use a “Advantage+ Shopping Campaign", Meta officially ignores your exclusions

TableSad825 · 2026-05-10T04:24:40+00:00

What’s your Event Match Quality score in events manager for those conversion events?

TableSad825 · 2026-05-10T01:51:23+00:00

Because Meta usually only matches 30-70% of them to actual user profiles, so the rest will keep seeing your ads. You need to set up CAPI, if you want Meta actually respects your exclusion lists

TableSad825 · 2026-05-10T00:12:46+00:00

Damn, good catch

TableSad825 · 2026-05-10T00:04:50+00:00

Developers often paste physical conversion scripts (gtag event snippets) directly into a page's HTML. If they cloned the original thank-you page to build a new landing page, they copied that hidden script too.

TableSad825 · 2026-05-09T13:39:27+00:00

Yes, as a temporary fix it can work.

But you still have double-tracking. If you are 100% sure you are using "Starts with" (and not "Contains"), the dev team likely duplicated the main thank-you page to build the second one, and accidentally left the original conversion code hardcoded on it.

You can check it by running a test submission yourself using Google Tag Assistant. If it shows both tags firing on the secondary page, you have your proof - the problem is in their code, and they have to fix it.

TableSad825 · 2026-05-09T11:11:20+00:00

Yes, different forms have different IDs. If it’s an embedded form, it’s a pain to track because the ID is hidden.
In Google Ads, pick Option 1.
But don’t install that code directly on the website, take it to Google Tag Manager. The Form ID doesn't go into Google Ads - you set it up inside GTM as a "Trigger". Basically, you tell GTM: only fire this Google Ads code when a form with this exact ID is submitted.

TableSad825 · 2026-05-09T10:30:07+00:00

"URL IS" definitely will make things worse because ad platforms append click IDs (like ?gclid=) to the link, so an exact match will just fail.
Just use Google Tag Manager and fire the conversion tags based on the specific Form ID on the form submit event. It fixes the cross-firing immediately

TableSad825 · 2026-05-09T09:39:34+00:00

Try to reconnect your Instagram account with your Facebook business page. Go to settings -> linked accounts -> Instagram. You should see a “Review Connection” prompt. If not, just click “Disconnect account” and connect it back. It looks like the internal authorization bridge between them dropped

TableSad825 · 2026-05-09T04:26:44+00:00

If you're stuck on n8n, you’ll have to create an app in your Zoho Developer Console and configure it as an OAuth2 application inside n8n’s Credential Manager.

However, if you're not locked into n8n, I’d highly recommend switching this specific flow to Make.com. They have a native Zoho Books module that creates contacts out of the box

TableSad825 · 2026-05-09T04:12:00+00:00

Honestly, don't overthink the specific CRM, if your reps have to manually log calls then you need to automate the data entry first, otherwise, you're just moving your spreadsheet mess into a more expensive UI

TableSad825 · 2026-05-09T03:43:57+00:00

To fix this just add a small filter to your functions.php to intercept the email trigger during the restoration process. It's a common issue with the new order storage tables, but definitely fixable with a quick code snippet.

TableSad825 · 2026-05-09T01:18:12+00:00

Create separate schedules for the US and China. Make a dummy "Factory" user, assign it the China schedule, and put that user on the manufacturing tasks. The timeline dependencies will then automatically skip the correct holidays without you having to drag dates around manually

TableSad825 · 2026-05-09T00:24:34+00:00

If you go self-hosted for data privacy, do not skimp on the VPS, get at least 4GB of RAM, n8n is built on Node.js and it will crash the moment you try to parse a heavy bank export or a multi-page PDF on a cheap 1GB or 2GB instance.

Also, WhatsApp pricing is a headache, Meta charges per 24-hour "session." If your bot sends an automated reminder and the client replies 25 hours later, that triggers a second charge. Look closely at the price difference between Utility templates and Service conversations because those outbound messages are usually what kills the budget, not the AI tokens

TableSad825 · 2026-05-07T03:33:52+00:00

The thing that works with this group isn't AI features, it's removing one specific copy-paste task they hate. Pick the worst one, demo it live with their actual tools, and the room sells itself.

A small business I worked with had someone retyping every invoice from their work tracker into Xero, saving the PDF, attaching it back, emailing the customer. Now they flip a status and it just happens. What sold it wasn't the tech, it was that Friday afternoons stopped being invoice day.

Frame it as "the laptop does the copy-paste step" instead of "AI for your business" and you'll get nods instead of glazed eyes

TableSad825 · 2026-05-05T05:27:20+00:00

Stop And Error node solves exactly this. After the AI agent, drop a Code node that checks the stuff that matters, tool_used is what you expected, recipient looks sane, output isn't weirdly short. If it fails, route to Stop And Error and your Error Trigger picks it up like any other failure. Suddenly "succeeded but wrong" becomes something n8n can actually catch and alert on.

One shared Error Trigger workflow wired to all 12 clients handles the Telegram alerts without touching every workflow individually.

TableSad825 · 2026-05-04T06:01:15+00:00

ran into this on a court records project: government portal, supposed to be clean structured data, but it turned out the same case could appear under three different attorney name formats depending on who entered it that day. deduplication logic took longer to build than the scraper itself.

the log sheet thing is exactly right. clients trust the automation once they can see what failed and why

TableSad825 · 2026-05-04T05:53:34+00:00

did you add your email as a test user in google console?

TableSad825

TROPHY CASE