Integration
Connect Handwrytten to UUID Generator
When something happens in Handwrytten, your agent does the next thing in UUID Generator. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Handwrytten and UUID Generator to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Handwrytten and UUID Generator
Triggers and actions 1 trigger ยท 13 actions
Trigger
Address ListTriggers when Recipient Addresses are needed.
Action
Add Order to BasketAdds an order to a basket. If sending multiple cards at once, use this for each order, then check-out with Send Basket
Action
Create ContactCreates a new address book entry for the Handwrytten address book. (Note: other zaps don't really use the address book, but the rest of Handwrytten does.).
Action
Create Custom CardCreates a new custom 5x7 card with full bleed cover, using specified images, fonts, and logos.
Action
Empty BasketClears your basket.
Action
Find ContactFinds a contact in your address book.
Action
Update ContactUpdates an entry in the Handwrytten address book.
Action
Upload Custom ImageAdds an image to Handwrytten for use in custom card designs.
Action
Decode UUIDDecode an existing UUID string to extract its version, variant, and (for time-based versions) the embedded timestamp. GET https://www.uuidtools.com/api/decode/{uuid} (endpoint inferred from the site's Decode UUID tool at /decode; confirm exact path when implementing).
Action
Generate timestamp-first UUIDGenerate one or more timestamp-first (ordered) UUIDs, where the current timestamp is embedded at the start so values sort in creation order when stored/indexed. GET https://www.uuidtools.com/api/generate/timestamp-first (endpoint path per the /generate/timestamp-first docs page).
Action
Generate v1 UUIDGenerate one or more (up to 100) time-based version-1 UUIDs. GET https://www.uuidtools.com/api/generate/v1 or /v1/count/{n}.
Action
Generate v3 UUIDGenerate a deterministic version-3 (MD5-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v3/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
Action
Generate v4 UUIDGenerate one or more (up to 100) random version-4 UUIDs. GET https://www.uuidtools.com/api/generate/v4 or /v4/count/{n}.
Action
Generate v5 UUIDGenerate a deterministic version-5 (SHA-1-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v5/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.