LinderConnectInstall

Summary

Create or update a location within an organization. If a location with the same orgId and name/slug already exists, it is updated with the provided fields; otherwise, a new location is created and its context, industryId, templateId, and promptSnapshotId are set via a subsequent PATCH.

Inputs

• orgId (required) — The organization ID to associate the location with.
• locationName (required) — The name of the location.
• locationSlug — Optional slug; derived from locationName (lowercase, dash-separated) if not provided.
• locationTimezone — Timezone for the location.
• locationStatus — Status of the location; defaults to draft.
• context — Context data as JSON; defaults to {}. Used for routing and metadata.
• industryId — Optional industry ID override.
• templateId — Optional template ID override.
• promptSnapshotId — Optional prompt snapshot ID override.

Output shape

The raw API response from LinderConnect. On creation, includes the new location's ID and details; on update, includes the modified location. The node outputs this as the main output data.

The execute() method returns [ { json: o } ] where o is the HTTP response from the final PATCH or POST call.

Examples

Example 1: Create a new location under an org.

Provide orgId, locationName; optional fields may be omitted. The operation POSTs a new location, then PATCHes context/industry/template/prompt/status.

Example 2: Update an existing location.

Provide orgId and locationName matching an existing location's org_id and name/slug. The operation GETs the locations list, finds the match, and PATCHes the provided fields.