When when an alkymi event triggers (return document information) in Alkymi, sync it to Delibr.
When Alkymi extracts document information, sync the extracted details to Delibr.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Delibr Explore Delibr →
TriggersFires when a new task, job or item is created in Delibr.
Fires when a task in Delibr is marked complete.
Fires when a task's due date in Delibr is coming up.
Fires when a task, job or project changes status in Delibr.
Creates a new task, job or item in Delibr.
Updates a task's status or assignee in Delibr.
Posts a comment on a task in Delibr.
Assigns a task in Delibr to a team member.
Alkymi Explore Alkymi →
TriggersFires when Alkymi finishes extracting data from a document such as an invoice, receipt, form or resume.
Posts a file to Alkymi to be parsed.
Runs an extraction template in Alkymi against a document.
Common questions
Can Knit build “When when an alkymi event triggers (return document information) in Alkymi, sync it to Delibr.” between Delibr and Alkymi?
Yes — describe it in the box above and Knit's Integrations Agent researches Delibr and Alkymi's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.