COCKPIT n8n INTEGRATION: AUTOMATE COCKPIT WITH N8N

The "Get a singleton" action retrieves a specific singleton resource from your Cockpit instance. Singletons in Cockpit are perfect for storing unique content like site settings, homepage configurations, or company information—content that exists only once and doesn't belong in a collection.

Key parameters:

• Credential to connect with: Select your pre-configured Cockpit account credentials from the dropdown menu. This is required for authentication.
• Resource: Automatically set to "Singleton"—this identifies the resource type you're accessing.
• Operation: Set to "Get"—defines the retrieval action.
• Singleton Name or ID: Text field where you enter the specific identifier for the singleton you want to retrieve. This is required.

Use cases:

• Fetch site-wide settings (logo, contact info, social links) to populate your frontend automatically
• Retrieve homepage hero content and pass it to a static site generator
• Pull company information for automated document generation or email signatures

The "Submit a form" action sends form data directly to Cockpit, enabling you to process submissions from external sources or create form entries programmatically. This is ideal for aggregating leads from multiple channels into Cockpit's form system.

Key parameters:

• Credential to connect with: Dropdown to select your Cockpit account credentials. Required.
• Resource: Pre-set to "Form" to indicate the resource type.
• Operation: Fixed to "Submit a Form"—no additional input needed.
• Form: Text field to specify which form receives the submission. Required.
• JSON Data Fields: Toggle switch to enable or disable sending data in JSON format. Optional.
• Form Data: Area to attach specific data fields corresponding to your form structure. Optional—click "Choose..." to select fields.

Use cases:

• Consolidate form submissions from landing pages, chatbots, and third-party tools into Cockpit
• Programmatically create form entries based on triggers from other applications
• Build multi-step forms where data from various sources merges into a single Cockpit form

The "Update a collection entry" action modifies an existing entry within a specified Cockpit collection. When your content needs to stay in sync across multiple systems, this action ensures your Cockpit data reflects the latest changes automatically.

Key parameters:

• Credential to connect with: Select your Cockpit credentials from the dropdown. Required.
• Resource: Set to "Collection" to target collection resources.
• Operation: Fixed to "Update an Entry."
• Collection Name or ID: Text field for the name or ID of the target collection. Required.
• Entry ID: Text field requiring the specific ID of the entry you want to update. Required.
• JSON Data Fields: Optional toggle to specify whether input data is in JSON format.
• Entry Data: Define the new data for the entry based on your collection's schema. Required.

Use cases:

• Sync product stock levels from your inventory system to Cockpit product collections
• Update blog post status when content is approved in an external editorial workflow
• Modify user profile entries when CRM data changes

The "Create a collection entry" action adds a new entry to a specified Cockpit collection. This is your go-to action for automating content creation—whether it's blog posts, products, team members, or any structured content type.

Key parameters:

• Credential to connect with: Dropdown for selecting your Cockpit account credentials. Required.
• Resource: Automatically set to "Collection."
• Operation: Fixed to "Create an Entry."
• Collection Name or ID: Text field where you input the target collection's name or ID. Required.
• JSON Data Fields: Boolean toggle to determine whether JSON data fields are used for entry data. Optional.
• Entry Data: Structured input for the new entry's content. Required—define fields matching your collection schema.

Use cases:

• Automatically create product entries in Cockpit when new items are added to your e-commerce platform
• Generate blog post drafts from content briefs submitted via other tools
• Add team member profiles when new employees are onboarded in your HR system

The "Get Many Collection Entries" action retrieves multiple entries from a specified Cockpit collection in a single operation. Perfect for bulk operations, reporting, or syncing large datasets to external systems.

Key parameters:

• Credential to connect with: Dropdown to select your Cockpit credentials. Required.
• Resource: Set to "Collection."
• Operation: Fixed to "Get Many Entries."
• Collection Name or ID: Text field for the collection you want to query. Required.
• Return All: Toggle to retrieve all entries from the collection. Optional.
• Limit: Numeric input setting the maximum number of entries returned (default: 100). Optional.
• Options: Additional configurable options for advanced filtering. Optional.

Use cases:

• Export all blog posts to a backup system or migrate content to another platform
• Generate reports by pulling product data for analysis in spreadsheet tools like Airtable
• Sync entire collections to search indexes like Algolia or Elasticsearch for enhanced search functionality