Integration
Connect Handwrytten to profileAPI
When something happens in Handwrytten, your agent does the next thing in profileAPI. 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 profileAPI 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 profileAPI
Triggers and actions 1 trigger ยท 11 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
Find Person by EmailFinds a uniquely identified person by passing an email address.
Action
Get Company by LinkedInUrlGets an enriched company profile by passing a LinkedIn url.
Action
Lookup phoneGiven a person or company identifier, find associated phone number(s). POST /2024-03-01/phone-contacts/lookup.
Action
Reverse lookup phoneGiven a phone number, find the associated person/company profile. POST /2024-03-01/phone-contacts/reverse-lookup.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.