InNotes icon

InNotes

Consume InNotes CRM API

Actions22

Job → Exists

AI-generated

Overview

This node operation checks if a job exists in the InNotes CRM system by searching for a given ID. It verifies the existence by first attempting to find the job by its Job ID, and if not found, it searches by the External ID. This operation is useful for validating job records before performing further actions, such as updates or deletions, ensuring that the job data is present in the system.

Use Case Examples

  1. Check if a job with a specific internal Job ID exists before updating its details.
  2. Verify the presence of a job using an external reference ID to avoid duplicate entries.

Properties

Name Meaning
ID The ID to search for, which will be checked against both the Job ID and the External ID in the system.
Options Additional options to control batch processing behavior, such as batch size and timeout between batches to avoid rate limiting.

Output

JSON

  • exists - Boolean indicating whether the job exists.
  • found_by - Indicates whether the job was found by 'job_id' or 'ext_id'.
  • id - The ID that was searched for.
  • error - Error message if the existence check failed.

Dependencies

  • Requires an API key credential for the InNotes CRM API to authenticate requests.

Troubleshooting

  • If the node returns 'exists: false', verify that the provided ID is correct and corresponds to either a Job ID or External ID in the system.
  • If an error occurs, check the API credentials and network connectivity to the InNotes CRM API.
  • Rate limiting issues can be mitigated by adjusting the batch size and timeout options.

Links

Discussion