What can I automate with the UUID Tools integration?

Make and read the identifiers that keep records from colliding, with UUID Tools. Get one unique ID or a batch of a hundred, as a plain random ID, one that sorts by when it was made so it works as a database key, or one that carries its own timestamp. Build a repeatable ID from a name - the same customer, domain or order number always gives the same ID, from any workflow, with no lookup table to keep - which is how two systems that share no IDs can still agree on one. And read an ID back to see which kind it is and, when it carries one, the moment it was made. Every ID is a standard UUID. No account or API key required. Lodol supports 3 actions for UUID Tools, which you can combine with any other app in a workflow.

How do I connect UUID Tools to Lodol?

Connect UUID Tools once in your workspace and every action and trigger it supports can be added to a workflow, by you in the editor or by your AI.

All integrationsUtilities

UUID Tools

Make and read the identifiers that keep records from colliding, with UUID Tools.

Start Free Browse all integrations

actions: 3

Actions

Steps a workflow can run in UUID Tools.

Generate unique IDsGet an identifier nothing else will ever share - one, or up to a hundred in a single step. It can be plainly random, sortable so newer IDs file after older ones in a database, or time-based so the moment it was made can be read back out of it. Every one is a standard UUID, so anything that takes a UUID or a GUID will take these. No API key required.
Generate a repeatable IDTurn a name into an ID that comes out exactly the same every time. Give it a web address, a domain, an email address or an order number and you get one ID for that thing - from any workflow, on any day, with no lookup table to keep. That is what makes it the way to line up records across two systems that have no ID in common: both sides work it out from the same name and land on the same ID. No API key required.
Inspect an IDRead an ID back and find out what it is: which kind, and - when it is a kind that carries one - the exact moment it was made and the machine that made it. The step fails if the value is not an ID at all, which makes it the way to check that something arriving from a form or another system really is one before the rest of the workflow leans on it. No API key required.