Flotiq
for LuumenAI
Read content types and objects in Flotiq, then publish changes as approved steps.
Connect Flotiq with an API key and Luumen can read your content types, list and filter objects, and search across everything the key can see. When something needs to change — a corrected field, a post that should go live — the agent shows the object and the edit first, then waits for your approval before writing.
The Flotiq toolbox
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Content ObjectGet one object by content type and ID, optionally expanding its relationships.
- ReadGet Content TypeGet one content type definition, including its field schema and metadata configuration.
- ReadList Content ObjectsList and filter objects from one Flotiq content type while preserving its dynamic fields.
- ReadList Content TypesList the content type definitions visible to the connected Flotiq account, including internal types.
- ReadSearch ContentFull-text search across content objects visible to the API key, optionally restricted to content types, with configurable matching, ordering, relationship expansion, and pagination.
- WriteBatch Upsert Content ObjectsCreate or update up to 100 objects of one Flotiq content type in a batch, returning success and error counts plus per-object validation errors. Approval by default
- WriteCreate Content ObjectCreate one object that conforms to a Flotiq content type definition. Approval by default
- WriteDelete Content ObjectSoft-delete one Flotiq content object. Approval by default
- WriteSet Content PublicationPublish a Draft & Public content object or return it to draft; this changes what public consumers can see. Approval by default
- WriteUpdate Content ObjectPartially update selected fields of one existing Flotiq content object. Approval by default
One prompt, start to finish
What a governed Flotiq run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as batch upsert content objects, create content object, delete content object, set content publication, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Flotiq — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Flotiq to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.