Update multiple contacts
Request body which must comply to the following JSON Schema:
{ "type" : "object", "properties" : { "contacts" : { "type" : "array", "description" : "List of contacts to be updated", "items" : { "type" : "object", "properties" : { "email" : { "type" : "string", "description" : "Email address of the user to be updated (For each operation only pass one of the supported contact identifiers. Email, id or sms)", "format" : "email", "example" : "elly@example.com" }, "id" : { "type" : "integer", "description" : "id of the user to be updated (For each operation only pass one of the supported contact identifiers. Email, id or sms)", "format" : "int64", "example" : 31 }, "sms" : { "type" : "string", "description" : "SMS of the user to be updated (For each operation only pass one of the supported contact identifiers. Email, id or sms)", "example" : "+91xxxxxxxxxx" }, "ext_id" : { "type" : "string", "description" : "Pass your own Id to update ext_id of a contact.", "example" : "UpdateExternalId" }, "attributes" : { "type" : "object", "additionalProperties" : { }, "description" : "Pass the set of attributes to be updated. **These attributes must be present in your account**. To update existing email address of a contact with the new one please pass EMAIL in attribtes. For example, **{ \"EMAIL\":\"newemail@domain.com\", \"FNAME\":\"Ellie\", \"LNAME\":\"Roger\"}**.\nKeep in mind transactional attributes can be updated the same way as normal attributes. Mobile Number in **SMS** field should be passed with proper country code. For example: **{\"SMS\":\"+91xxxxxxxxxx\"} or {\"SMS\":\"0091xxxxxxxxxx\"}**\n", "example" : { "EMAIL" : "newemail@domain.com", "FNAME" : "Ellie", "LNAME" : "Roger" } }, "emailBlacklisted" : { "type" : "boolean", "description" : "Set/unset this field to blacklist/allow the contact for emails (emailBlacklisted = true)", "example" : false }, "smsBlacklisted" : { "type" : "boolean", "description" : "Set/unset this field to blacklist/allow the contact for SMS (smsBlacklisted = true)", "example" : true }, "listIds" : { "type" : "array", "description" : "Ids of the lists to add the contact to", "items" : { "type" : "integer", "description" : "Id of the list to add the contact to", "format" : "int64", "example" : 65 } }, "unlinkListIds" : { "type" : "array", "description" : "Ids of the lists to remove the contact from", "items" : { "type" : "integer", "description" : "Id of the list to remove the contact from", "format" : "int64", "example" : 36 } }, "smtpBlacklistSender" : { "type" : "array", "description" : "transactional email forbidden sender for contact. Use only for email Contact", "items" : { "type" : "string", "format" : "email" } } } } } } }
Specify how the response should be mapped to the table output. The following formats are available:
Raw Response: Returns the raw response in a single row with the following columns:
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Brevo from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.