ActiveMerge
for LuumenAI
Generate documents and images from your ActiveMerge templates, one approved job at a time
Connect ActiveMerge and your agent can see the document templates, image templates, and workflows your account already has, along with the exact placeholder names each one expects and the credits left on the plan. Generation runs as a previewed step you approve, and finished output can be saved to cloud storage. Authentication is by API key.
The ActiveMerge toolbox
13 tools: 9 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet CreditsGet total, used, remaining, plan, and prepaid ActiveMerge credits before running credit-consuming generation tools.
- ReadGet Document GenerationsGet one document-generation job by ID, or list and filter generation history when no job ID is supplied.
- ReadGet Document Template PlaceholdersReturn the case-sensitive placeholder names required by one document template.
- ReadGet File Download URLCreate a temporary download URL for a file in ActiveMerge cloud storage.
- ReadGet Image GenerationGet an image-generation job's progress, credit usage, errors, and temporary ZIP download URL when complete.
- ReadGet Image TemplatesList image templates and basic placeholders, or get complete dimensions, positions, defaults, and styles for one template when template_id is supplied.
- ReadGet WorkflowsList available ActiveMerge workflows, or return the case-sensitive placeholders for one workflow when workflow_id is supplied.
- ReadList Document TemplatesList document templates available to the connected ActiveMerge account, including the unique template IDs needed for placeholder lookup and generation.
- ReadList Stored FilesList the immediate files and folders at the ActiveMerge cloud-storage root, or directly inside parent_folder_id when supplied.
- WriteGenerate DocumentStart asynchronous document generation from a template and case-sensitive placeholder data. Approval by default
- WriteGenerate ImagesStart an asynchronous image-generation job from inline JSON records. Approval by default
- WriteGenerate Workflow DocumentsGenerate documents for every template in an ActiveMerge workflow using case-sensitive placeholder data. Approval by default
- WriteSave Generated FilesSave non-expired output from a completed document-generation job to permanent ActiveMerge cloud storage. Approval by default
One prompt, start to finish
What a governed ActiveMerge 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.
Read actions answer immediately. Anything that writes — generate document, generate images, generate workflow documents, save generated files — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 ActiveMerge — 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 ActiveMerge to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.