BeLazy
Project ManagementConnect AI agents to BeLazy, integration middleware for the translation industry supply chain. Agents watch vendor portals for new opportunities, accept or dismiss them, add deliverables to projects, and stage files in a workspace.
What This Integration Enables
BeLazy is the layer between the portals that hand out translation work and the business management system a language service provider actually runs on. The unusual thing about connecting an agent to it is that BeLazy sits on the accepting side of a commercial relationship. Most connectors let an agent read a system or write a record. This one lets an agent take on an obligation: accept an opportunity and you have committed a deadline, a language pair and a price to a client who is now waiting.
That shapes how the connector should be used. FlowRunner covers both directions BeLazy supports. In the business management system direction, agents pull accepted projects, acknowledge that they were created on your side, set pricing, assign vendors to pricing items, register deliverables and start delivery. In the project ingestion direction, where your own system plays the vendor portal, agents stage files in a workspace, turn them into a priced opportunity, then collect deliverables and close the project once the BMS is finished with it. Around both sit the vendor portal connections, the nine BMS configuration lists that BeLazy maps against, and the language and specialization reference data.
Two boundaries are worth stating before you design a flow. This connector has no triggers. BeLazy does send webhooks, but its own documentation states that setting them up through the API is not supported: callback URLs, headers and event types are configured by hand in the BeLazy profile menu, and no subscription endpoint exists. So a flow that reacts to new work is polling List Opportunities filtered to Ready and List Projects filtered to Accepted, paging with the nextId cursor. Your polling interval is your response time, and the account limit of 100 requests per minute is the ceiling on how tight you can make it. The second boundary is the credential. A BeLazy token carries the full rights of the user who created it, and the vendor publishes no scopes and no read-only token type, so a connection that can list opportunities can also accept them, assign vendors, deliver projects and overwrite your mapping lists. Create a dedicated integration user rather than pointing FlowRunner at a project manager's account.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Offers arrive pre-judged instead of pre-accepted
A scheduled flow calls List Opportunities filtered to Ready and pages forward with nextId. For each new ID it calls Get Opportunity, which returns the language pair, the pricing items, the deadline and the end customer, and it calls Get Vendor Portal Connection to establish which portal the offer came from. It then applies the rules the studio already has and has never been able to automate: which language pairs you staff internally, what turnaround you will accept for a given word count, which end customers are on credit hold. Offers that clearly fail are summarized in a daily digest rather than interrupting anyone. Everything else goes to the resourcing owner in Slack as one message with the deadline in local time and the rule it passed. Nothing is accepted by the flow itself.
Driving a business management system BeLazy does not support natively
When your BMS is not one BeLazy integrates with directly, projects sit in the Accepted state waiting for you. A flow polls List Projects filtered to Accepted, calls Get Project for the destination representation already mapped to your own values, creates the matching project in your system, then calls Acknowledge Project Creation with your identifier and link so BeLazy can cross reference the two. From there it calls Set Project BMS Pricing with the agreed total, Set Project Vendors to record who is doing which pricing item, and Download Project File to pull the translatable material into Google Drive for the linguist. The point is not that the steps are hard. It is that they are a five-call sequence that a coordinator currently performs by hand, project after project, and that gets skipped when the day gets busy.
Pushing work out of a proprietary system into the supply chain
A marketing team approves a batch of content in Airtable that needs six target languages. A flow calls Create Workspace, then Upload File and Add File To Workspace for each source document with the target language set on the file, then Create Opportunity From Workspace with the pricing items attached. The content is now in the translation supply chain without anyone opening a portal. When the work comes back, the flow calls List Project Deliverables and Download Project Deliverable to collect each translated file into FlowRunner file storage, then Close Project to mark it finished on the ingestion side. One caution the connector surfaces deliberately: Upload File puts bytes into temporary storage that is discarded after ten minutes if nothing references them, so the attach step has to follow promptly rather than sit behind an overnight batch.
Human-in-Loop Highlight
Accept Opportunity is where this connector stops being an integration and starts being a commitment. Accepting turns an offer into a project with a deadline your team now owes a client, and the opposite choice is worse to get wrong: Dismiss Opportunity removes the offer from consideration permanently, and the API accepts no further action on a dismissed opportunity. There is no un-accept and no un-dismiss. Meanwhile the token doing the calling has the full rights of whoever created it, so nothing in BeLazy will stop a flow from saying yes to a fortnight of work you cannot staff. So the agent does the part that is genuinely tedious and stops at the part that is genuinely a decision. It assembles the offer from Get Opportunity, resolves the portal with Get Vendor Portal Connection, checks the deadline against the calendar, and posts one message: "New offer from the Acme portal, English to Japanese, 14,200 words, due Thursday 09:00 local. Rate is 8% under our floor for this pair. Accept, or dismiss permanently?" A named person answers, and the agent calls Accept Opportunity or Dismiss Opportunity on that instruction. It then polls Get Opportunity until state.projectId is populated, because acceptance returns instantly while project creation does not, which is exactly the kind of detail a person should not have to remember at 8am.
Agent Capabilities
58 actionsOpportunities
9- List Opportunities Lists translation work offered to your organization but not yet accepted, with every opportunity property. Filters combine with AND, so an opportunity must match all of them. Page forward by passing the returned nextId back as the cursor. With no triggers available, this is the polling entry point for new work.
- Get Opportunity Retrieves a single opportunity with everything BeLazy holds: source and target languages, pricing items, deadline, end customer and current status. Because BeLazy webhook payloads carry IDs only, this is the call that turns a bare notification into something a person can judge.
- Accept Opportunity Accepts an offered opportunity, creating a BeLazy project and starting its transfer into your business management system. Acceptance is instant but project creation is not, so the returned state may still carry a null projectId. Poll Get Opportunity until state.projectId appears before acting on the project.
- Dismiss Opportunity Dismisses an offered opportunity so it is ignored and no longer available for acceptance. This cannot be undone through the API. A dismissed opportunity accepts no further action of any kind.
- Update Opportunity Properties Updates the editable properties of an opportunity: deadline, end customer, specialization, contact person and custom extra data. Only supplied values are written and empty values are skipped, so it cannot be used to blank a field. Applies only while the opportunity status is Ready.
- Create Opportunity From Workspace Creates an opportunity from files already staged in a workspace, which is how a proprietary vendor portal pushes work into BeLazy. Identify files by ID or by tag, never both, and omit both to create an opportunity with no files. When your BMS is Plunet, include at least one pricing item or the Plunet items and jobs are not created.
- List Opportunity Files Lists metadata for every file attached to an opportunity, including name, type, size and whether the content can be downloaded. Files arriving through a connection are only fetched from the portal at project creation, so availableForDownload is commonly false until the opportunity is accepted.
- Get Opportunity File Retrieves the metadata of one file attached to an opportunity without transferring its content. Use it to check type, size and download availability before spending a download.
- Download Opportunity File Downloads the content of a file attached to an opportunity into FlowRunner file storage and returns a URL for later steps. Typically succeeds only once availableForDownload is true.
Projects
11- List Projects Lists accepted work with full detail. Each project carries three representations of the same data: origin as it arrived, beLazy unified, and destination mapped to your own values. Work with destination unless you need the raw source. Note that filtering for Accepted status also filters on acceptance time, defaulting to the last week.
- Get Project Retrieves one project with every current detail, including all three representations, pricing items, mapped workflow and status. The pricing item IDs read here are what the vendor assignment and partial delivery actions expect.
- Acknowledge Project Creation Confirms to BeLazy that an accepted project now exists in your own business management system, moving it from Accepted to Transferred. Supply your identifier and link so BeLazy can cross reference it, and optionally the total price. This applies only to a REST API business management system.
- Set Project BMS Pricing Adds or replaces the total price of a project as represented in your business management system. Applies once the project has been accepted and acknowledged, and only while it is not yet delivering or terminated.
- Deliver Project Signals that the whole project has been delivered on your side, starting final delivery and close in the vendor portal. Once called, deliverables can no longer be uploaded or modified for this project. Register every deliverable with Add Project Deliverable first.
- Deliver Project Item Starts delivery of one pricing item so its registered deliverables are uploaded, leaving the rest of the project open. Those deliverables are locked afterwards, and the project delivers itself automatically once the last item goes. Portals without partial delivery reject this with a 405.
- Close Project Signals that a project was successfully delivered and closed in your proprietary vendor portal, marking it closed in BeLazy. This is the final step of the project ingestion direction, called after your system has collected the deliverables.
- Dismiss Project Dismisses a project so BeLazy ignores it and stops monitoring it. Use it to drop work that was accepted in error or that will be handled outside BeLazy entirely.
- List Project Files Lists metadata for every file attached to a project, including which pricing items and BMS jobs each file belongs to. A file with availableForDownload false is not permanently stored, which happens when the source connection lacks the permanent storage option.
- Get Project File Retrieves the metadata of one project file without transferring its content, including its pricing item association and download availability.
- Download Project File Downloads the source or reference content of a project file into FlowRunner file storage and returns a URL. This is how a REST API business management system collects the translatable material for work it has just been assigned.
Vendor Assignment
4- Set Project Vendors Assigns vendors to several pricing items at once so BeLazy can apply the matching linguist assignment in the origin system through its vendor mapping. Only the named pricing items change. Returns a 409 if linguist assignment is switched off for any of them.
- Set Project Vendor Assigns a vendor to a single pricing item, with the same mapping behavior and the same 409 when linguist assignment is disabled for that item.
- Set Project Origin Vendors Assigns linguists to the origin pricing items of a workspace project so BeLazy can apply the matching vendor assignment in your business management system. Applies to workspace projects with the linguist assignment in BMS option enabled.
- Set BeLazy Vendor For Pricing Item Assigns a vendor already stored in BeLazy to a pricing item, identified by its BeLazy vendor ID rather than a business management system ID. The vendor marks this endpoint as preview and may change it without notice.
Deliverables
5- List Project Deliverables Lists the translated files registered against a project with name, type, size, source and target language and the pricing item each belongs to. A BMS uses it to review what it uploaded; a proprietary portal uses it to discover what is ready to collect.
- Get Project Deliverable Retrieves the metadata of one registered deliverable without transferring its content, including its pricing item, file type and the language in both representations.
- Add Project Deliverable Registers an already uploaded file as a deliverable, or updates the properties of one already registered. Upload the bytes with Upload File first and pass the returned ID here. Registering does not start delivery.
- Download Project Deliverable Downloads the content of a registered deliverable into FlowRunner file storage and returns a URL. This is how a proprietary vendor portal collects the finished translation once the BMS has delivered.
- Remove Project Deliverable Removes a registered deliverable from a project. Only possible before the pricing item it belongs to has started delivering, because delivery locks its deliverables against modification.
Workspaces
10- List Workspaces Lists the staging areas that hold translatable content before it becomes an opportunity. Name and tag matching are both case sensitive, and when several tags are given a workspace must carry all of them.
- Get Workspace Retrieves the name and tags of one workspace. Use it to confirm a workspace exists and carries the expected tags before staging files into it.
- Create Workspace Creates a staging area for translatable content, the first step of pushing work into BeLazy from a proprietary system. A workspace carries at most 20 tags.
- Update Workspace Replaces the properties of a workspace. This is a full overwrite, so tags omitted from the request are cleared rather than kept. Read the current values with Get Workspace first if you only mean to change one.
- Delete Workspace Permanently deletes a workspace together with every file staged in it, and cannot be reversed. Refused with a 409 when the workspace still has unapproved projects or unused files, unless Force is enabled.
- Get Workspace Settings Retrieves the automation settings saved against a workspace, which drive how opportunities created from it are handled. Returns 404 when the workspace exists but has no settings. Marked preview by the vendor, so its body is returned verbatim.
- List Workspace Files Lists the files staged in a workspace with name, type, size, tags and target language. Name, external ID and tag matching are all case sensitive.
- Get Workspace File Retrieves the properties of one staged file, including type, size, tags and target language. Use it to confirm a file was added with the right type before building an opportunity from it.
- Add File To Workspace Attaches an already uploaded file to a workspace and sets its properties, or updates them if it is attached already. Must happen inside the ten minute window before unreferenced uploads are discarded. Name and File Type are both required.
- Remove File From Workspace Removes a file from a workspace so it is no longer available for building opportunities. Opportunities already created from the file are unaffected.
Files
2- Upload File Uploads file content into BeLazy temporary storage and returns a file ID for later calls such as Add File To Workspace or Add Project Deliverable. Fetches the bytes from the URL you supply. Unreferenced files are discarded after ten minutes and the maximum accepted size is 3 GB.
- Delete File Discards a file from BeLazy temporary storage. Offered for convenience when an upload was a mistake, since a file you intend to use should simply be referenced and unreferenced uploads clear themselves anyway.
Vendor Portal Connections
4- List Vendor Portal Connections Lists the vendor portal and translation management system connections configured in your organization, with portal URL, the user the connection runs as, and when it last synchronized. Only connections marked isAutomated can be synchronized on demand.
- Get Vendor Portal Connection Retrieves one connection with its portal URL, running user, automation flag and last synchronization timestamp. Use the last sync time to decide whether an on demand sync is worth requesting at all.
- Synchronize Connection Queues a full synchronization so BeLazy fetches all currently available projects from the portal. The call returns before the work finishes. Rejected with a 429 when the connection was synchronized within the last three minutes or a sync is still pending, and with a 400 when the connection is not automated.
- Synchronize Project From Connection Queues synchronization of one named project rather than sweeping the whole portal. Identify the project by external ID or portal URL. Documented for Lionbridge TMS, Lokalise, Transifex, TranslatedNet, Phrase TMS and memoQ connections.
Business Management System Projects
4- Get BMS Project Retrieves a business management system project tracked by BeLazy together with the opportunities and projects bundled into it. Two views are available: jobs and tasks. Jobs is the default and the only view available when the project does not support tasks.
- Set BMS Job Linguists Assigns linguists to open jobs in one call. Accepted with a 202, so it confirms that the change was scheduled rather than applied. Read back with Get BMS Project to confirm. Marked preview by the vendor.
- Set BMS Job Deadline Changes the deadline of a single open job. Accepted with a 202 and applied asynchronously, so it confirms scheduling rather than completion. A job that is not open is rejected with a 400.
- Close BMS Job Closes an open job, marking that workflow step finished. Accepted with a 202 and applied asynchronously. A job that is not open is rejected with a 400.
Business Management System Settings
6- Get BMS Settings Retrieves every configuration list BeLazy holds for your business management system in one response: clients, languages, project managers, rates, services, specializations, units, vendors and workflows. These lists are the pool of values available when someone builds a mapping rule, so a value missing here cannot be mapped to.
- Overwrite BMS Settings Replaces all nine configuration lists in a single call. Any list omitted from the request is emptied. Prefer the sub-setting actions unless you genuinely mean to replace everything.
- Reset BMS Settings Clears every configuration list and re-enables editing of those lists in the BeLazy user interface, which is otherwise locked to read only while the API supplies them. Mapping rules referencing cleared values stop resolving, so repopulate before running further automation.
- Get BMS Sub-Setting Retrieves one configuration list by name. Clients, languages, project managers, services, specializations, units and vendors come back as identifier to label maps; rates as an array of strings; workflows as an array of objects with a name and its workflow steps.
- Overwrite BMS Sub-Setting Replaces one configuration list. A full overwrite, so values absent from the request are removed and any mapping rule referencing them stops resolving. Match the shape that list uses.
- Append To BMS Sub-Setting Adds entries to one configuration list without disturbing what is there. This is the safe way to register a newly created client, vendor or service, and it returns the full list after the append.
Vendors and Reference Data
3- List BeLazy Vendors Lists the vendors stored in BeLazy with names, email addresses, usernames and the identifier they carry in your business management system. Marked preview by the vendor and may change without notice.
- List Languages Lists every language code BeLazy recognizes. Language values elsewhere accept any string, but using a code from this list gives BeLazy the best chance of mapping automatically instead of requiring a manual mapping in the web application.
- List Specializations Lists every specialization, also called domain, that BeLazy recognizes. As with languages, using a recognized value improves the odds of automatic mapping.
Frequently Asked Questions
What can FlowRunner do with BeLazy?
FlowRunner agents can run List Opportunities, Get Opportunity, and Accept Opportunity in BeLazy, plus 55 more actions.
Does connecting BeLazy to FlowRunner require OAuth?
No. BeLazy connects to FlowRunner with an API key, no OAuth flow required.
Can BeLazy trigger a FlowRunner workflow automatically?
BeLazy doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with BeLazy
$100 in credits. No card required. Connect in minutes.