> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/issue-syncing/create-a-sync-profile.md). # Create a sync profile Create inbound and outbound sync profiles to map fields between Cortex AgentiX issues and external applications. Sync profiles provide a blueprint for how information is exchanged between Cortex AgentiX issues and external applications, by defining field mapping. This ensures that relevant data, such as **Status** or **Description**, is accurately transferred and maintains consistency, even if the systems use different terminology. When you link an issue with an external application (such as Jira), or set up an automation, you can select the sync profile you want to use. Cortex AgentiX provides default outbound and inbound sync profiles, or you can create custom sync profiles as described in the following procedure. How to create a sync profile 1. Go to **Settings** → **Configurations** → **Object Setup** → **Issues** → **Sync Profiles**. 2. Click **New Profile**. 3. Type a profile name and description. 4. Under **Integration**, select the external application with which you want to map fields, such as Jira V3 or ServiceNow V2. 5. Under **Sync Direction**, select **Inbound** or **Outbound**. If you select **Inbound**, you will define field mapping from the external application to Cortex AgentiX. If you select **Outbound**, you will define field mapping from Cortex AgentiX to the external application.

Note

If an issue is using bi-directional syncing, you need to provide both an Inbound and an outbound sync profile.

6. Under **Field Mapping**, select a field to map and select the corresponding field. For example, Jira: Priority, Cortex: Severity. 7. Define one or more values for each field that you want to map.

Note

8. Click **Save**. Example In this example, the sync profile specifies Inbound mapping from Jira v3 fields to Cortex fields. ![Sync\_profile\_example.png](https://404732257-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FocwvgxtzkvBHMLbPsZuG%2Fuploads%2Fgit-blob-56ef61bdbc2dfd2c2bda4ba0285e62008f1e4501%2F053eb012a06adcbc9feebb449ef1949a784deff31c746a3e69ca4c197f36cb15.png?alt=media) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/issue-syncing/create-a-sync-profile.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.