post-connection-enable-custom-fields

Enable custom field selection for connected systems via Merge's Field Mapping API.

Updated May 7, 2026
One-click install
npx skills add https://github.com/merge-api/merge-unified-skills --skill post-connection-enable-custom-fields
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-connection-enable-custom-fields
Source: https://github.com/merge-api/merge-unified-skills/tree/main/skills/post-connection-enable-custom-fields
Command: npx skills add https://github.com/merge-api/merge-unified-skills --skill post-connection-enable-custom-fields

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a user interface for customers to select and enable custom fields from their connected systems using Merge's Field Mapping API, enhancing their data management capabilities.

Core Features & Use Cases

  • Custom Field Selection: Allows customers to choose which custom fields from their connected systems to enable.
  • Field Mapping API Integration: Leverages Merge's Field Mapping API for dynamic field mapping.
  • Approach Flexibility: Offers two approaches (Remote Data and Field Mapping API) for field configuration.

Quick Start

Use the post-connection-enable-custom-fields skill to enable custom fields for your HR/ATS/CRM integration.

Frequently Asked Questions about post-connection-enable-custom-fields

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable custom fields for a connected HRIS system?

To enable custom fields for a connected HRIS system, use this Skill to select and map fields from your linked system via Merge's Field Mapping API. It provides an interface for data customization within your specific integration.

What is the difference between Remote Data and Field Mapping API approaches for data customization?

The difference between Remote Data and Field Mapping API approaches lies in their configuration methods for custom fields. This Skill offers both approaches, allowing you to dynamically map data from connected systems based on your specific integration requirements.

Do I need an Enterprise plan to use the Merge Field Mapping API for custom field selection?

Yes, you need an Enterprise plan to access the full Field Mapping API features. This Skill leverages the API to enable custom fields, requiring the Enterprise tier to utilize complete dynamic field mapping capabilities for connected systems.

Can I configure custom fields for an ATS integration after establishing a connection?

Yes, you can configure custom fields for an ATS integration post-connection. This Skill enables custom field selection for linked systems, allowing you to manage and map data dynamically using Merge's Field Mapping API.

What are the limitations of using Field Mapping API for custom field data customization?

A primary limitation of using the Field Mapping API is that full features require an Enterprise plan. While the Skill facilitates custom field selection and data mapping, access to the complete API capabilities is gated behind this subscription tier.