Contentful integration

Quick start

Call Contentful from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Contentful's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "CONTENTFUL_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for Contentful. End-users click Connect on the integration card in your app, complete the OAuth flow with Contentful, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2, API_KEY.

Available actions

106 actions exposed via the Contentful integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• CONTENTFUL_ACTIVATE_CONTENT_TYPE
• CONTENTFUL_ARCHIVE_ASSET
• CONTENTFUL_ARCHIVE_ENTRY
• CONTENTFUL_ARCHIVE_RELEASE
• CONTENTFUL_CREATE_APP_DEFINITIONS_KEYS
• CONTENTFUL_CREATE_CONTENT_TYPE
• CONTENTFUL_CREATE_ENTRY_TASK
• CONTENTFUL_CREATE_ENVIRONMENT
• CONTENTFUL_CREATE_ORGANIZATIONS_APP_DEF_ACCESS_GRANTS
• CONTENTFUL_CREATE_ORGANIZATIONS_APP_DEFINITIONS
• CONTENTFUL_CREATE_ORGANIZATIONS_APP_DEFINITIONS_ACTIONS
• CONTENTFUL_CREATE_ORGANIZATIONS_INVITATIONS