I’m building a webhook integration to create call transcript records with rich text content via API. I’ve hit multiple roadblocks and need guidance on the correct approach.
Initial Attempt - Single API Call: I tried creating entities with rich text content directly using formats like:
“Purple Crow CRM/Call Summary”: “plain text content”
“Purple Crow CRM/Call Summary”: {“Collaboration~Documents/content”: “HTML content”}
Both failed with “Entity reference should contain fibery/id key” errors, suggesting rich text fields expect entity references to existing documents, not inline content.
Current Understanding: Based on API documentation, rich text fields require a two-step process:
-
Create entity (which auto-creates empty Document entities)
-
Update document content using document secrets
Since I couldn’t get the initial API call to work by itself and it appeared that it wouldn’t work unless the entity already existed, I tried to just use two different API functions. One that writes the calls, and the second to add the rich text data (because it seemed like it wouldn’t work the other way)
Step 1 works: Create entities successfully via /api/commands
Then I tried and was successful:
Query works: Can retrieve document secrets like “01997147-1b50-7061-a6af-1a3607a3cfdc”
Step 2 fails: Cannot find working commands for /api/documents/commands
Commands tested (all return “Command not found”):
-
update-documents
-
set-document-content
-
create-or-update-documents
-
Is my understanding correct that rich text fields cannot accept inline content and require the two-step approach?
-
If so, what is the correct command syntax for updating document content via /api/documents/commands?
-
If not, what’s the correct format for creating rich text content in a single API call?
Use case: Call full transcript integration where large text content needs to be stored in rich text fields for analysis and reporting.
**Bottom Line: I’m trying to push all the call data and the meta data, but I can’t figure out how to store any large text sets in rich text fields.
**
Fibery’s built-in Email integration successfully syncs email content into rich text fields, which suggests this functionality exists somewhere in the system.
How does the Email integration populate rich text fields with large content?
Is there a different API endpoint, authentication method, or data format that built-in integrations use that external webhooks should also use?
Question: Can external integrations access the same rich text creation capabilities that built-in integrations like Email sync use?