Active with remarks |
---|
This application needs additional settings. Please follow the documentation below to create your own connectionUnique, active service acces point to a network. There are different types of connections (API key, Oauth…). More. |
The Lexoffice modulesThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More allow you to monitor, create, update, send, retrieve, upload, download, list, and download the documents, contacts, vouchers, and invoices in your Lexoffice account.
Prerequisites
-
A Lexoffice account – create a Lexoffice account at lexoffice.de/.
Connecting Lexoffice to Boost.spaceCentralization and synchronization platform, where you can organize and manage your data. More IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. More
To connect your Lexoffice account to Boost.space Integrator you need to obtain the API Key from your Lexoffice account and insert it in the Create a connection dialog in the Boost.space Integrator moduleThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More.
1. Go to this API Key website and log in to your Lexoffice account.
2. Click Create key new > Accept the terms and conditions > Create keys.
3. Copy the API Key to your clipboard.
4. Go toBoost.space Integrator and open the Lexoffice module’s Create a connection dialog.
5. In the Connection name field, enter a name for the connection.
6. In the API Key field, enter the API key copied in step 3, and click Continue.
The connection has been established.
TriggersEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... when an event occurs are followed by the event type parameter.
Note | |
---|---|
You do not have to add the webhooksA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. in the Lexoffice as it is automatically done for you once you add and save an instant triggerEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... module to your scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. More. |
WebhookA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. Name |
Enter a name for the webhook. |
Connection |
|
Event Type |
Select or map the event types you want to watch. For example, |
Uploads a document for bookkeeping purposes.
Connection |
|
Filename |
Enter (map) the filename with extension. For example, |
Data |
Enter (map) file data. |
Downloads a document.
Connection |
|
Document /File ID |
Enter (map) the document ID or File ID you want to download. |
Searches for contacts by a filter parameter.
Connection |
|
|
Enter (map) the email address of the contact. |
Name |
Enter (map) the contact’s name. |
Number |
Enter (map) the contact’s phone number. |
Customer |
Select whether the contact is a customer to search for the customers that match the specified contact. |
Vendor |
Select whether the contact is a vendor to list the vendors that match the specified contact. |
Limit |
Set the maximum limit Boost.space Integrator should return during one execution cycleA cycle is the operation and commit/rollback phases of scenario execution. A scenario may have one or more cycles (one is the default).. |
Gets a specified contact.
Connection |
|
Contact ID |
Select or map the Contact ID whose details you want to retrieve. |
Creates a new contact.
Connection |
|||||||||||||
Contact Type |
Select or map the contact type:
|
||||||||||||
Salutation |
Enter (map) the contact’s salutation. For example, |
||||||||||||
Name |
Enter (map) the company name. |
||||||||||||
First Name |
Enter (map) the contact’s first name. |
||||||||||||
Last Name |
Enter (map) the contact’s last name. |
||||||||||||
Tax Number |
Enter (map) the contact’s or company’s registered tax number. |
||||||||||||
Allow Tax Free Invoices |
Select whether you want to allow the tax-free invoices for the company or contact. |
||||||||||||
VAT Registration ID |
Enter (map) the company’s VAT registration number. |
||||||||||||
Contact Persons |
Add the contact persons of the company:
|
||||||||||||
Roles |
Select the contact or company roles. For example, |
||||||||||||
Addresses |
Add the addresses of the contact or the company:
|
||||||||||||
Email Addresses |
Add the email addresses of the contact or the company: Type Select or map the email address type. For example, |
||||||||||||
Phone Numbers |
Add the phone numbers of the contact or the company: Type Select or map the phone number type. For example, |
||||||||||||
Buyer Reference |
Enter (map) the Customer’s Leitweg-ID conforming to the German XRechnung system. |
||||||||||||
Vendor Number At Customer |
Your vendor number is used by the customer. This field is applicable when you are providing the Buyer Reference number. |
||||||||||||
Note |
Enter (map) the additional information about the contact. |
Updates an existing contact.
Connection |
|||||||||||||
Contact ID |
Select or map the Contact ID whose details you want to update. |
||||||||||||
Contact Type |
Select or map the contact type:
|
||||||||||||
Salutation |
Enter (map) the contact’s salutation. For example, |
||||||||||||
Name |
Enter (map) the company name. |
||||||||||||
First Name |
Enter (map) the contact’s first name. |
||||||||||||
Last Name |
Enter (map) the contact’s last name. |
||||||||||||
Tax Number |
Enter (map) the contact’s or company’s registered tax number. |
||||||||||||
Allow Tax Free Invoices |
Select whether you want to allow the tax-free invoices for the company or contact. |
||||||||||||
VAT Registration ID |
Enter (map) the company’s VAT registration number. |
||||||||||||
Contact Persons |
Add the contact persons of the company:
|
||||||||||||
Roles |
Select the contact or company roles. For example, |
||||||||||||
Addresses |
Add the addresses of the contact or the company:
|
||||||||||||
Email Addresses |
Add the email addresses of the contact or the company: Type Select or map the email address type. For example, |
||||||||||||
Phone Numbers |
Add the phone numbers of the contact or the company: Type Select or map the phone number type. For example, |
||||||||||||
Buyer Reference |
Enter (map) the Customer’s Leitweg-ID conforming to the German XRechnung system. |
||||||||||||
Vendor Number At Customer |
Your vendor number is used by the customer. This field is applicable when you are providing the Buyer Reference number. |
||||||||||||
Note |
Enter (map) the additional information about the contact. |
Searches for vouchers with a voucher number.
Connection |
|
Voucher Number |
Enter (map) the voucher number whose details you want to search. |
Limit |
Set the maximum number of vouchers Boost.space Integrator should return during one execution cycle. |
Retrieves a list of vouchers.
Connection |
|
Voucher Type |
Select or map the voucher type. For example, |
Voucher StatusCreate statuses for each module separately to create an ideal environment for efficient and consistent work. More |
Select or map the voucher status. For example, |
Archive |
Select whether you want to search the archived vouchers. |
Sort |
Select or map the option to sort the list the vouchers. For example, |
Limit |
Set the maximum number of vouchers Boost.space Integrator should return during one execution cycle. |
Creates a new voucher.
Connection |
|
Voucher Type |
Select or map the voucher type. For example, |
Voucher Status |
Select or map the voucher status. For example, |
Archive |
Select whether you want to search the archived vouchers. |
Sort |
Select or map the option to sort the list of vouchers. |
Uploads a file and assigns it directly to a voucher.
Connection |
|
Voucher ID |
Select or map the Voucher ID to which you want to upload a file. |
File Name |
Enter (map) the file name with extension. For example, |
Data |
Enter (map) the file data. |
Gets a specified
Connection |
|
Invoice ID |
Select or map Invoice ID whose details you want to retrieve. |
Renders an invoice document to a file ID.
Connection |
|
Invoice ID |
Select or map the document’s Invoice ID you want to render. |
Performs an authorized arbitrary API call.
Connection |
|
URL |
Enter a path relative to For the list of available endpoints, refer to the Lexoffice API Documentation. |
Method |
Select the HTTP method you want to use:
|
Headers |
Enter the desired request headers. You don’t have to add authorization headers; we already did that for you. |
Query String |
Enter the request query string. |
Body |
Enter the body content for your API call. |
The following API call returns all the contacts from your Lexoffice account:
URL:
/v3/contacts
Method:
GET
Matches of the search can be found in the module’s Output under BundleA bundle is a chunk of data and the basic unit for use with modules. A bundle consists of items, similar to how a bag may contain separate, individual items. More > Body > content.
In our example, 3 contacts were returned: