The Nedzo public API now takes tags and custom fields when you create, upsert or update a contact. Your app can send a lead to Nedzo with the right tags and data in one call.
Before, the contacts API took four things: first name, last name, email and phone. But you sort and follow up on leads by their tags and custom fields. So you sent the lead, then went into Nedzo and tagged it by hand. Or you skipped that step, and the lead sat there with half its data missing.
Add tags via the API
Every contact call now takes an optional list of tags. That goes for create, upsert and update.
Say a lead fills in your "free quote" form. Your app sends the contact to Nedzo with a "quote request" tag. The lead shows up in Nedzo already tagged and ready for your follow up.
Contacts API custom fields
Each call also takes an optional set of custom field values. You send the field and the value, and Nedzo saves it on the contact.
Nedzo checks every field you send against the custom fields in your workspace. If you send a field that doesn't exist, Nedzo rejects the call with a 400 error. You find out right away, so you don't lose data without knowing it.
Upsert a contact without losing data
The upsert call has a setting called preserveExisting. It now works for custom fields too.
- Set it to true and Nedzo fills only the empty custom fields. The data you already have stays put.
- Leave it off and Nedzo writes the new values over the old ones. That's the default.
So your app can push the same lead twice, and you decide which data wins.
Tags and custom fields come back on reads
When you read a contact through the API, you now get its tags and custom fields back. The API docs for the create, upsert and update endpoints cover the new fields.
It's live in your account now.