Requesting an integration
What to do when the tool you need is not in the library yet.
If the tool you need isn't in the integration library, tell us. Every request is recorded, and the tools that get asked for most are the ones that get built next.
How to send a request
Go to the contact page and fill in the form. Say which tool you want and what you'd use it for — the section below covers what makes that description useful.
You don't need an account to send one, and there's no limit on how many you can send.
What happens to it
Every request is logged against the tool it names, so repeat requests for the same tool add up rather than sitting in separate inboxes.
That count is the main thing driving what gets built. When several people ask for the same integration, it moves up the queue; a tool nobody else has asked for waits longer. So if the tool you need is already popular, your request genuinely helps — it isn't a duplicate, it's a vote.
How to write a helpful request
A request naming only the tool is a vote. A request describing the workflow is something that can be built, tested, and shipped correctly the first time. Four things make the difference:
Name the tool precisely, with a link. Product names overlap and vendors ship several products under one brand. A link to the exact product page removes the guesswork.
Say which direction you need. This is the most important detail:
- Something in that tool should start an automation → you need a trigger
- Nodest should do something in that tool → you need an action
They're very different amounts of work, and an integration built for the wrong direction is no use to you.
Link the tool's API documentation. If you can find it, include it. It decides whether the integration is possible at all and how much of it can be built.
Describe the workflow, not just the tool. "When someone books in Acme Scheduler, add them to my Brevo list" tells us far more than "please add Acme Scheduler". Sometimes it also reveals a shorter path to what you want using tools that are already supported, and we can tell you that instead of making you wait.
Why some tools arrive with actions only
Worth knowing, because it explains a partly-fulfilled request.
For Nodest to do something in a tool, that tool needs an API. Most have one.
For Nodest to react to something, the tool has to be able to notify an outside service when something changes — usually through webhooks. Plenty of otherwise capable tools simply can't do that.
Where that's the case, the integration ships with actions and no triggers, and you'd start those automations from somewhere that does have triggers, usually your WordPress site. It isn't an oversight; the tool doesn't offer the hook.
While you wait
Three things worth checking:
- Is an adjacent tool already supported? If the data you need also lives somewhere Nodest connects to, you may be able to work from there.
- Do you only need an action? If the missing tool just has to receive data, your automation can start elsewhere — a smaller gap than a full integration.
- Can the tool be driven by something you already produce? Some services accept email or inbound data that another step could send.
