What each resource is for
Resolve the resource before changing a setting
Choose the resource from the selected location’s list when configuring a feature. Check the location as well as the name: two calendars with the same name can belong to different businesses. For contact fields and custom values, open CRM context fields. For a tag action, decide whether it happens during the call or after the call.Master agents
Master agents share configuration while binding calendars, transfer destinations and pipeline stages per project. Read bindings before rolling out a change. A successful name match must still resolve to the child’s actual resource; an unresolved binding must not be reported as ready.In the API
The platform does not proxy CRM reads. Take the ids from GoHighLevel and pass them to Update campaign (trigger tags,config.calendarId), Update agent
(contextFields) or
Add actions to an outcome
(tag, stage and calendar ids on nodes).