Tripletex Make integrationAutomate Tripletex with Make.

Adds a new client record to Tripletex from data another app already holds, so nobody copies a name, an address or an email by hand before invoicing can start.

Gives you a new label to sort clients in Tripletex, for instance by region, segment or sales channel, without opening the settings screens yourself.

Opens a new account in your Tripletex chart of accounts straight from a scenario, which helps when several entities or projects need the same accounts set up.

Registers a new way of paying out money in Tripletex, the payment type your team selects when settling supplier bills, so the option is ready before the first payment goes out.

Books a new voucher in the Tripletex ledger, the accounting document behind an entry, so figures coming from another system land in the books without manual keying.

Turns a sale captured elsewhere into an order in Tripletex, ready to be invoiced, so the sales team and accounting look at the same document.

Creates an order group in Tripletex so related orders sit together instead of floating as separate documents that someone has to match later.

Adds one line to an existing Tripletex order, which is how a basket of several products becomes a complete order instead of a single lump sum.

Puts a new item in the Tripletex product register from your catalog source, so orders and invoices can reference it without anyone retyping names and prices.

Sets up a new product family in Tripletex so your catalog stays organized the same way it is in your shop or inventory tool.

Links one product to one product group in Tripletex, which is the step that actually places an item inside a family.

Records a new place where a product is stocked in Tripletex, so inventory figures point to the right shelf, warehouse or shop.

Adds a unit of measure in Tripletex, such as a box, an hour or a kilo, so products can be sold in the quantity that matches how you really deliver them.

Opens a project in Tripletex the moment a job is confirmed, so hours, orders and costs have a place to land from the first day.

Creates a relative VAT type in Tripletex from a scenario, useful when your tax setup has to be reproduced on several accounts in the same way.

Adds an item you buy from a vendor to Tripletex, so purchasing uses the supplier's catalog without manual entry.

Marks a company-wide day off in the Tripletex timesheet, so nobody gets flagged for missing hours on a date the whole office was closed.

Logs hours in Tripletex from wherever people actually track their time, a form, a task tool or a time tracker, so billable work reaches accounting without double entry.

Adds a salary type specification to the Tripletex timesheet, which tells payroll how a block of hours should be paid.

Removes a customer from Tripletex, which keeps the register clean when a record was created by mistake or duplicated by another flow.

Takes an account out of the Tripletex chart of accounts, handy when a scripted setup created one too many and you want to undo it in the same tool.

Removes an outgoing payment type from Tripletex, so a closed bank account or abandoned channel stops appearing when bills are paid.

Deletes a voucher from the Tripletex ledger, useful to roll back an entry that an automated flow booked by mistake.

Removes an order group from Tripletex when the batch it represented is cancelled or was created twice.

Drops one line from a Tripletex order, the simplest way to reflect an item the customer removed from the basket.

Removes a product family from Tripletex once a range is discontinued, so the catalog stops showing empty or outdated groups.

Unlinks a product from a group in Tripletex while keeping both the product and the group, which is how you move an item from one family to another.

Removes a stock location from a product in Tripletex once that item is no longer kept there.

Deletes a unit of measure you no longer use in Tripletex, which keeps the unit list short when people pick one by hand.

Removes a project from Tripletex, mostly to clean up projects opened automatically for deals that fell through.

Takes an item out of a vendor's catalog in Tripletex, so buyers no longer see products the supplier has stopped selling.

Removes a company day off from the Tripletex timesheet, so people can log hours normally again on that date.

Erases a logged block of hours in Tripletex, which keeps timesheets honest when the source entry is removed in another tool.

Removes a salary type specification from the Tripletex timesheet, so hours are no longer paid under a category that was assigned in error.

Fetches the full record of one Tripletex customer, so the next modules can reuse its details in an email, a CRM update or a document.

Reads one customer category from Tripletex, so a scenario can route a client differently depending on the segment it belongs to.

Pulls the details of one account from the Tripletex chart of accounts, so you can check it before booking anything on it.

Retrieves one accounting period from Tripletex, so a scenario knows which period a date belongs to before it books anything.

Reads one annual account from Tripletex, handy for a reporting scenario that needs the yearly frame of your books.

Fetches one ledger close group from Tripletex, so a scenario can pass what that group contains to another tool for review.

Pulls one outgoing payment type from Tripletex, so the next module knows exactly how money leaves the company for this record. You get a single bundle, the item that flows to the next module, ready to map.

Brings back one posting line from the Tripletex general ledger, the smallest unit of your bookkeeping. Once it lands in Make, you can copy its values into a spreadsheet, a message or a report module.

Reads one VAT type as it is configured in Tripletex, so later modules apply the rate and code your books already use instead of a value typed by hand in the scenario.

Opens one voucher from your Tripletex ledger and hands its content to Make as a single bundle. From there you can archive it, forward it or compare it with what another tool recorded.

Returns one voucher type, the category Tripletex uses to sort entries such as purchases or bank transactions. Your scenario then knows which kind of voucher it is handling.

Loads the monthly timesheet of an employee from Tripletex, with the hours already logged, so you can reuse them in payroll prep, a client report or a message to a manager.

Fetches one external product, an item Tripletex keeps outside your own catalog, and exposes its data to the next module in your scenario.

Retrieves the details of one invoice from Tripletex, so the amounts, customer and lines can travel to a CRM, a dashboard or a reminder email without retyping.

Returns one incoming payment type, the way a customer settles an invoice in Tripletex.

Reads one sales order from Tripletex with its header data, so your scenario can pass it to a shipping tool, a shared channel or a follow-up task.

Pulls one order group, the way Tripletex bundles several orders together, and gives your scenario the group data to route or report on.

Brings back one line of an order: the product, the quantity and the price as Tripletex stores them. It is the finest level of detail you can read on a sale.

Loads one product from your Tripletex catalog, so its name, price and settings can feed an online shop, a quote tool or a price list.

Returns one product group, the family Tripletex uses to organize items in your catalog, and makes its data available to later modules.

Reads one relation, the link that says a given product belongs to a given group in Tripletex. Your scenario learns where an item is filed.

Fetches one inventory location for a product, the place in your stock where Tripletex expects to find it, and hands it to the next module.

Returns one product unit, such as a piece, an hour or a box, as defined in Tripletex. Later modules can then show quantities with the right unit.

Reads one unit master, a unit from the Tripletex reference list, so your scenario works from the standard list rather than a custom one.

Opens one Tripletex project and passes its data to your scenario, so a project tool, a chat channel or a report stays in line with your accounting.

Retrieves one supplier product, an item you buy from a vendor as Tripletex records it, with the data you need to reorder or compare.

Returns one company holiday from the Tripletex timesheet setup, so a planning tool or a team calendar can respect days off the company already declared.

Loads one timesheet entry, a block of hours someone logged in Tripletex, so you can reuse it for billing, approval or a project update.

Reads one salary type specification linked to timesheets, the rule that tells Tripletex how certain hours are paid, and exposes it to your scenario.

Fetches one time clock record, the punch in and punch out data Tripletex keeps for attendance, and makes it available to later modules.

Brings back the weekly timesheet of an employee from Tripletex, giving you the hours of one week in a single bundle to forward or check.

Reads the logistic settings of your Tripletex company, the options that shape how stock and deliveries behave, and shares them with the rest of your scenario.

Returns the timesheet settings of your Tripletex account, so a scenario that logs hours can follow the rules your company chose.

Calls any endpoint of the Tripletex API from your scenario, reusing the connection you already set up. It covers what the listed modules leave out.

Changes an existing customer record in Tripletex with the data your scenario brings, so your accounting mirrors what sales or support just learned.

Edits a customer category, the label Tripletex uses to group clients, so your segments follow changes decided elsewhere.

Modifies an account of your Tripletex chart of accounts with values sent by the scenario, keeping your ledger aligned with decisions taken in another tool.

Adjusts an outgoing payment type in Tripletex, so the way the company pays suppliers matches the latest bank setup.

Changes an existing voucher in your Tripletex ledger, for example to complete it with data that arrived after it was created.

Writes a new value into your company logistic settings in Tripletex, so stock and delivery options follow a decision made outside the app.

Changes the monthly timesheet of an employee in Tripletex, useful when the month has to be adjusted as a whole rather than line by line.

Edits an existing sales order in Tripletex with new data from your scenario, so the order follows what the customer or your team just changed.

Modifies an order group in Tripletex, the container that bundles several orders, so the batch reflects the latest decision.

Adjusts one line of an order in Tripletex, such as the quantity or the price agreed with the customer, without rebuilding the whole order.

Changes a product in your Tripletex catalog, so names, prices or settings stay identical to the source you trust, a web shop or a supplier sheet.

Renames or edits a product group in Tripletex, keeping your catalog families in step with how your shop or your team organizes them.

Keeps the record of where a product sits in your stock accurate, by editing an inventory location Tripletex already knows instead of adding a second one next to it.

Corrects a product unit you created earlier, the way Tripletex counts what you sell (pieces, hours, boxes), without rebuilding it from scratch.

Refreshes a project that already lives in Tripletex, so the list your team books hours against matches what was decided in your other tools.

Supplier products are the items you buy from vendors. This module edits one of them in Tripletex, so your purchasing data follows what the vendor actually sells today.

Moves or corrects a company holiday already registered in the Tripletex timesheet calendar, rather than deleting it and entering it again.

Fixes hours already logged: a timesheet entry is one line of time booked by an employee, and this module rewrites that line in place.

Adjusts a salary type specification that exists in the timesheet side of Tripletex, so payroll settings stay aligned with what HR decided.

Corrects a time clock record stored in Tripletex timesheets, so the clocked hours match what really happened on the floor.

Works on a whole week instead of a single line: it modifies a weekly timesheet that already exists in Tripletex.

Brings older accounting documents into Tripletex by uploading them as historical vouchers, which helps when bookkeeping moves over from another system.

Returns the customer categories set up in Tripletex, filtered or as a full list, so the scenario picks the right label before it files a customer.

Tells the scenario whether a customer already exists in Tripletex, which is the simplest way to avoid creating the same client twice.

Pulls the external products registered in Tripletex, either those matching your criteria or all of them, so a scenario can compare references before it adds anything.

Hands the scenario invoice data from Tripletex, for a few specific invoices or the whole list, so other tools can use it without anyone exporting a report.

Lists the payment types that invoices can use in your Tripletex setup, or filters them, so the scenario works with the exact type your accountant configured.

Brings back the accounting periods of your Tripletex ledger, so a scenario can check them before it books anything.

Looks through your chart of accounts in Tripletex and returns the accounts that match, which lets a scenario map outside data to the right account.

Returns the annual accounts stored in your Tripletex ledger, filtered or in full, giving a reporting scenario the list of fiscal years it can work with.

Surfaces the close groups recorded in the Tripletex ledger, the same objects Get a Ledger Close Group reads one at a time.

Finds the outgoing payment types defined in Tripletex, the ways your company pays money out, so the scenario can reuse one instead of guessing.

Reads the individual lines booked in your Tripletex ledger and sends them to the scenario, ready for a report or another tool.

Returns ledger data from Tripletex, filtered or listed in full, when a scenario needs the broad view of the books rather than single lines.

Lists the VAT types configured in Tripletex, so every line a scenario writes carries the tax treatment your accountant set up.

Looks up vouchers, the accounting documents of your Tripletex ledger, and returns those that match what the scenario asks for.

Returns the voucher types Tripletex uses to classify accounting documents, so a scenario chooses one from the real list instead of from memory.

Pulls the order groups stored in Tripletex, which tells the scenario whether a group already exists before it files an order under it.

Finds orders in Tripletex by your criteria, which gives the scenario the exact order to update, read or attach lines to.

Shows which products are attached to which product groups, since a product group relation is exactly that link.

Lists the product groups of your Tripletex catalog, or only those matching a name, so new items land in a group that really exists.

Tells the scenario where products are stored by returning the inventory locations recorded in Tripletex.

Retrieves product prices from Tripletex, so a web store, a quote tool or a spreadsheet can show the same figures as your accounting.

Checks your Tripletex catalog for products that match a reference or a name, which is the step that keeps orders tied to real items.

Returns product unit masters, a separate list from the product units you define yourself (Search Product Units covers those).

Finds the product units you created in Tripletex, so a scenario that adds products can reuse the right one.

Returns the Tripletex projects that match your criteria, giving the scenario the project record it needs before logging time or changing details.

Lists the supplier products registered in Tripletex, or the ones matching your criteria, so purchasing data can be compared or corrected.

Pulls logged hours out of Tripletex, one bundle per timesheet entry, ready to be summed, reported or sent to another tool.

Lists the salary type specifications registered in Tripletex timesheets, so a payroll scenario starts from the settings that really exist.

Reads time clock records from Tripletex, the clock data behind your timesheets, and passes them to the rest of the scenario.