Creatio No-Code CRM and BPM REST API

Creatio no-code CRM and business process management REST API for enterprises to manage sales automation, marketing automation, customer service, and business process workflows — built on Creatio's no-code process engine — enabling automated lead management, opportunity tracking, case management, workflow orchestration, and customer journey automation through Creatio's composable CRM and BPM platform. Enables AI agents to manage contact management for customer and lead record creation and update automation, handle opportunity management for sales pipeline and deal lifecycle automation, access case management for customer service ticket and SLA management automation, retrieve campaign management for marketing campaign and email automation, manage process management for BPMN workflow creation and execution automation, handle product catalog for product and service catalog management automation, access reporting for CRM analytics and custom report automation, retrieve order management for sales order and invoice management automation, manage partner management for channel partner and distributor relationship automation, and integrate Creatio with ERP, telephony, and marketing platforms for CRM and BPM automation.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Other creatio no-code CRM BPM sales-automation customer-service-platform
⚙ Agent Friendliness
52
/ 100
Can an agent use this?
🔒 Security
74
/ 100
Is it safe for agents?
⚡ Reliability
64
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
10
Documentation
68
Error Messages
64
Auth Simplicity
72
Rate Limits
58

🔒 Security

TLS Enforcement
97
Auth Strength
70
Scope Granularity
64
Dep. Hygiene
68
Secret Handling
68

No-code CRM/BPM. SOC2, GDPR, ISO27001. OAuth2. US/EU. Customer and process data.

⚡ Reliability

Uptime/SLA
64
Version Stability
68
Breaking Changes
62
Error Recovery
62
AF Security Reliability

Best When

A mid-market or enterprise B2B company wanting AI agents to automate sales, marketing, and customer service CRM workflows along with BPMN-based business process orchestration through Creatio's no-code composable CRM and BPM platform.

Avoid When

CREATIO LICENSE REQUIRED: Creatio is commercial SaaS; automated open-source assumption creates license_required; Creatio requires subscription; automated must have Creatio plan. OBJECTS ARE CREATIO-SPECIFIC: Creatio data model uses Creatio-specific entity names (Contact, Lead, Opportunity, Activity); automated generic-CRM assumption creates entity_not_found for entities named differently than standard Creatio objects; automated must use Creatio entity names exactly. NO-CODE PROCESSES MUST BE DESIGNED FIRST: Business processes must be designed in Creatio's BPMN designer before API execution; automated api-first assumption creates process_not_found for process execution without pre-built process definition; automated must design processes in Creatio Studio before triggering via API. OData IS THE QUERY PROTOCOL: Creatio REST API uses OData for data querying; automated standard-REST assumption creates filter_syntax_error for queries not using OData filter syntax ($filter, $select, $expand); automated must use OData query syntax.

Use Cases

  • Automating sales pipeline management and opportunity tracking for CRM sales automation agents
  • Orchestrating customer service workflows and SLA management for contact center automation agents
  • Managing marketing campaigns and lead nurturing workflows for marketing automation agents
  • Building and executing no-code business process workflows for operations automation agents

Not For

  • Large enterprise requiring deep SAP or Oracle integration complexity (Creatio is mid-market to enterprise CRM; SAP CX or Salesforce serve complex SAP integration needs better)
  • Developer-first API-only integrations without CRM context (Creatio is CRM+BPM platform; pure API platforms serve pure-integration use cases)
  • E-commerce and retail-heavy customer engagement (Creatio is B2B and B2C service CRM, not e-commerce-native platform)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
Yes

Authentication

Methods: oauth2 basic
OAuth: Yes Scopes: No

Creatio uses OAuth2 for CRM and BPM REST API. REST API with JSON (OData protocol). Boston, MA HQ. Founded 2002 as Terrasoft (Ukraine). Rebranded Creatio 2019. $68M raised. Products: Creatio Sales (CRM), Creatio Marketing, Creatio Service, Creatio Studio (no-code). 6,000+ customers in 100+ countries. Recognized in Gartner CRM Magic Quadrant. Industries: financial services, logistics, pharma, professional services. Competes with Salesforce, Microsoft Dynamics, and Pega for CRM and BPM.

Pricing

Model: subscription
Free tier: Yes
Requires CC: No

Boston MA / Kyiv UA origin. $68M raised. 6,000+ customers. 14-day free trial. CRM+BPM no-code platform.

Agent Metadata

Pagination
page
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ODATA FILTER IS REQUIRED FOR QUERIES: Creatio REST API uses OData query syntax for filtering and selection; automated standard-REST assumption creates all_records_returned for queries without $filter parameter; automated must use OData $filter, $select, and $expand for targeted data retrieval
  • ENTITY NAMES ARE PASCAL CASE: Creatio entities use PascalCase naming (Contact, Lead, ActivityParticipant); automated snake_case assumption creates entity_not_found for entity names not matching Creatio PascalCase convention; automated must use correct PascalCase entity names
  • PROCESS SIGNALS ARE ASYNC: Business process execution via signal is asynchronous; automated sync-process assumption creates missed_completion for processes not tracked to completion via polling; automated must implement process completion monitoring
  • LOOKUP VALUES REQUIRE ID NOT TEXT: Creatio lookup fields require the lookup record ID, not the display text; automated text-value assumption creates lookup_not_found for lookups using display values instead of GUIDs; automated must resolve lookup display values to IDs before setting field values
  • FILE ATTACHMENTS ARE BINARY: Creatio file attachment upload requires multipart/form-data; automated JSON-only assumption creates upload_failure for file attachments not using multipart encoding; automated must use multipart/form-data for file attachment operations

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Creatio No-Code CRM and BPM REST API.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered