Surense

Interact with Surense API

Actions36

Activity Actions
- Create an Activity
- Search Activities
Contact Actions
Customer Actions
Data Proxy Actions
- Create Data Proxy
Document Actions
Employer Actions
- Delete an Employer
- Search Employers
Lead Actions
Meeting Actions
Meeting Summary Actions
- Create a Meeting Summary
- Send a Meeting Summary
Report Actions
- Generate a Report
- Send a Report
Workflow Actions

Contact → Update a Contact

AI-generated

Overview

The node named "Surense" provides integration with the Surense API, allowing users to interact with various Surense resources such as Contacts, Activities, Customers, Employers, Leads, Meetings, Documents, Reports, and Workflows. Specifically, for the Contact resource and the Update a Contact operation, this node enables updating details of an existing contact by specifying its unique Contact ID and optionally modifying additional contact parameters.

This node is beneficial in scenarios where you need to programmatically update contact information stored in Surense, such as changing phone numbers, emails, names, roles, or other metadata. For example, it can be used in automated workflows that synchronize contact data from other systems or update contact records based on user input or events.

Properties

Name	Meaning
Contact ID	The unique identifier (UUID format) of the contact to update.
Additional Parameters	Optional fields to update on the contact, including:
	- Primary email address (`email1`)
	- Secondary email address (`email2`)
	- Contact notes (`notes`)
	- Primary phone number (`phoneNumber1`)
	- Secondary phone number (`phoneNumber2`)
	- Company ID (`companyId`)
	- Employer ID (UUID format) (`employerId`)
	- Extension number (`extensionNumber`)
	- Whether the contact is shared (`shared`) [boolean]
	- Fax number (`faxNumber`)
	- Last name (`lastName`)
	- First name (`firstName`)
	- Contact description (`description`)
	- Role or position (`role`)

Output

The node outputs an array of JSON objects representing the result of the update operation for each input item. Each output JSON object typically contains the updated contact data returned from the Surense API after the update request is processed.

If the node encounters an error during execution and the "Continue On Fail" option is enabled, the output will include an error message within the JSON under an error field corresponding to the failed item.

No binary data output is indicated for this operation.

Dependencies

Requires an active connection to the Surense API.
Requires an OAuth2 API credential configured in n8n for authentication with Surense.
No other external dependencies are explicitly required.

Troubleshooting

Common issues:
- Invalid or missing Contact ID: The Contact ID must be provided in UUID format; otherwise, the API will reject the request.
- Insufficient permissions or invalid API credentials may cause authorization errors.
- Providing invalid data types or malformed values in additional parameters could lead to API validation errors.
Error messages:
- Errors returned from the Surense API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages might include "Contact not found," "Invalid UUID format," or "Unauthorized."
Resolution tips:
- Verify the Contact ID is correct and exists in Surense.
- Ensure the OAuth2 credential is valid and has necessary scopes.
- Validate all additional parameter values before sending the request.

Links and References

Surense API Documentation (hypothetical link as no direct URL was provided)
n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/

SurenseInstall