> ## Documentation Index
> Fetch the complete documentation index at: https://docs.teamfollowup.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the public API base URL: https://api.teamfollowup.ai/api.
> Authenticate public API requests with Authorization: Bearer YOUR_API_KEY.
> Use product-owned terms: agents, campaigns, projects (GoHighLevel sub-accounts), contacts, calls, outcomes, skills, cadences, phone numbers.
> Scope requests by locationId rather than projectName.
> Read the guide linked from each API reference group before recommending an endpoint.

# CRM resources

> Use the correct location's fields, values, calendars, tags and pipelines.

CRM resources belong to a location. Two locations may use the same display name
for different calendars, pipelines or fields.

## What each resource is for

| Resource | Used for |
| - | - |
| Custom fields | Contact-specific information the agent can use. |
| Custom values | Business information shared within the location. |
| Calendars | Booking or callback configuration. |
| Tags | Campaign enrollment, exclusions and in-call or post-call actions. |
| Pipelines and stages | Moving the contact through the business process. |

## 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](/agents/crm-context-fields). For a tag action, decide
whether it happens [during the call](/skills/tool-library) or
[after the call](/campaigns/after-the-call).

## Master agents

Master agents share configuration while binding calendars, transfer
destinations and pipeline stages per project. Read
[bindings](/campaigns/master-agent/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](/api-reference/campaigns/update-campaign) (trigger
tags, `config.calendarId`), [Update agent](/api-reference/agents/update-agent)
(`contextFields`) or
[Add actions to an outcome](/api-reference/campaigns/add-actions-to-an-outcome)
(tag, stage and calendar ids on nodes).