How to update the NAME of a Lexware contact?

Questions
1

:bullseye: What is your goal?

I want to automatically update the name of a Lexware contact when updating it in HubSpot.

:thinking: What is the problem & what have you tried?

I’ve setup a series of modules to watch the companies in HubSpot, load their name but the “Update a Contact” module from “Lexware Office” doesn’t have a field for the name. It has fields for a lot of other stuff but not the name. So how can I update this properly through the API?

I was thinking about using the module “Make an API Call” but Lexware doesn’t seem to support PATCH requests. With a PUT request, I would have to send through a bunch of data otherwise I’d lose data in Lexware.

:link: Create public scenario page

https://eu2.make.com/public/shared-scenario/UqGY9No6JL7/integration-hub-spot-crm-lexware-office

2

Hi @LeonR,

Based off the Lexware API docs and your message, the only way to update contacts in Lexware is through the PUT request. That leaves you no other choice than fetching the contact first to get the current values and then the Make an API call where you supplement the name with whatever you like and then updating the customer in Lexware

Cheers,

Henk

3

Hi Henk, thanks for the feedback. I almost thought that this would be the only option. Not sure why Make doesn’t include some of these properties in the update module. Since this manual procedure bears too many risks and might require updating in the future when the API updates, I’ve simply created a module for sending out a logging email that shows in case there are variables that haven’t been updated.

4

It could very well be the case that the update a contact module in Make does two things in one go already: 1) fetch the contact and replace any mapped fields to 2) PUT the whole resource to Lexware. Modules can execute multiple calls without it being visible in the scenario and still costing 1 credit.

I know this pattern exist, I assume this is also true for Lexware. Precisely because this is a risky pattern, I suppose they want to mitigate the risk and only make some of the fields available for update.

Again, I am not a Lexware user and I assume the workings of the module. Sometimes you need to find a workaround like the one you described.