CONTENTFUL n8n INTEGRATION: AUTOMATE CONTENTFUL WITH N8N

The "Get space" action retrieves detailed information about your Contentful space, including its name, default locale, and system metadata. This is your foundational action for validating connections and gathering space-level configuration data.

Key parameters:

• Credential to connect with: Select your configured Contentful account credentials from the dropdown—this is required for authentication.
• Source: Choose "Delivery API" to access published content or "Preview API" for draft content.
• Resource: Automatically set to "Space" for this action.
• Operation: Set to "Get" to retrieve the space details.

Use cases:

• Verify your Contentful connection is working at the start of complex workflows
• Pull space metadata to dynamically configure downstream actions
• Log space information for audit trails or monitoring dashboards

This action is ideal as a workflow health check or when you need to confirm which space your automation is targeting before proceeding with content operations.

The "GetAll locale" action fetches multiple locale entries from your Contentful space in a single request. This is essential for multilingual content workflows where you need to understand available languages and their configurations.

Key parameters:

• Credential to connect with: Required dropdown to select your Contentful account credentials.
• Source: Choose "Delivery API" for published locale data.
• Resource: Set to "Locale" to target locale entries.
• Operation: Set to "Get Many" to retrieve multiple locales at once.
• Environment ID: Text field specifying which Contentful environment to query (commonly "master").
• Return All: Toggle to fetch all available locales without pagination limits.
• Limit: Numeric input (default 100) controlling how many locales to return if "Return All" is disabled.

Use cases:

• Build dynamic translation workflows that adapt to your available locales
• Generate locale-aware content routing logic in your automations
• Sync locale configurations to external translation management systems

Use this action when setting up internationalization workflows or when you need to programmatically discover which languages your Contentful space supports.

The "Get entry" action retrieves a specific content entry from Contentful using its unique Entry ID. This is your go-to action for pulling individual pieces of content—blog posts, product pages, landing page sections, or any content type in your space.

Key parameters:

• Credential to connect with: Required dropdown for Contentful account selection.
• Source: "Delivery API" for published entries or "Preview API" for drafts.
• Resource: Set to "Entry" for content entries.
• Operation: Set to "Get" for single entry retrieval.
• Environment ID: Required text field for the target environment (e.g., "master").
• Entry ID: The unique identifier of the entry you want to fetch—accepts static text or dynamic expressions.
• Additional Fields: Expandable section for optional parameters like locale selection.

Use cases:

• Fetch a specific blog post entry to syndicate to social media platforms
• Retrieve product content to update inventory systems
• Pull landing page content for A/B testing analysis workflows

This action shines when you know exactly which entry you need—perhaps triggered by a webhook containing the Entry ID, or when processing a list of entry IDs from another system.

The "Get contentType" action retrieves the schema definition of a specific content type from your Contentful space. This gives you field names, field types, validation rules, and other structural information about how content is organized.

Key parameters:

• Credential to connect with: Required dropdown for authentication credentials.
• Source: "Delivery API" for content type definitions.
• Resource: Automatically set to "Content Type."
• Operation: Set to "Get" for single content type retrieval.
• Environment ID: Required text field (typically "master").
• Content Type ID: The identifier of the content type to fetch (e.g., "blogPost", "product").
• Additional Fields: Optional parameters for extended configuration.

Use cases:

• Dynamically build forms or interfaces based on Contentful content type structure
• Validate incoming data against content type field definitions before creating entries
• Document your content model by extracting all content type schemas programmatically

Use this action when you need to understand the structure of your content—particularly useful for building dynamic integrations that adapt to content model changes.

The "Get Many Assets" action retrieves multiple assets (images, videos, documents, files) from your Contentful space in a single request. Perfect for bulk operations on media files.

Key parameters:

• Credential to connect with: Required dropdown for Contentful account credentials.
• Source: "Delivery API" for published assets.
• Resource: Set to "Asset" for media file retrieval.
• Operation: Set to "Get Many" for bulk retrieval.
• Environment ID: Text field for environment specification (default "master").
• Return All: Toggle to fetch all assets without pagination.
• Limit: Numeric input (default 100) for controlled batch sizes when "Return All" is off.
• Additional Fields: Optional filters and query parameters.

Use cases:

• Sync all images from Contentful to a CDN or backup storage like Dropbox
• Generate asset reports with metadata for your media library
• Feed asset URLs into image optimization pipelines

This action is ideal for media management workflows, asset audits, or when you need to process your entire asset library through external services.

The "Get asset" action fetches a single asset from Contentful using its unique Asset ID. Use this when you need detailed information about a specific image, video, or file.

Key parameters:

• Credential to connect with: Required dropdown for credential selection.
• Source: "Delivery API" for published asset data.
• Resource: Set to "Asset."
• Operation: Set to "Get" for individual asset retrieval.
• Environment ID: Required text field for environment targeting.
• Asset ID: Required text field for the specific asset's unique identifier.

Use cases:

• Pull asset metadata (dimensions, file size, URL) for downstream processing
• Retrieve specific images to attach to emails or notifications via Gmail
• Validate asset existence before referencing in other content operations

Use this action when processing asset-specific events—like a webhook notification about an asset update—or when your workflow needs precise asset data for a known Asset ID.