Requested by the Lindy team

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/Components-attio-1e3bf548bb5e81d29a88c7801c148ba8

Hi @vunguyenhung @sergio-eliot-rodriguez I'm actually having issues with create-update-record action. I tried to make it work with just curl commands but I couldn't. This is the request I built

curl -X PUT https://api.attio.com/v2/objects/people/records?matching_attribute=record_id \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"data": {"values": {"record_id": "7d97721a-057a-50a3-a7d8-5626e0120283", "name": "Test 8 upd"}}}'

And this is the response I'm gerring with error:

{
  "status_code": 400,
  "type": "invalid_request_error",
  "code": "system_edit_unauthorized",
  "message": "Attempted to write to a protected attribute with slug/ID \"record_id\"."
}

@sergio-eliot-rodriguez can you help me out and contact support so maybe they can give us some clue about this error

The docs are here just in case https://docs.attio.com/rest-api/endpoint-reference/records/assert-a-record

hi @vunguyenhung about the issue:

Sources

Improvement needed - Deactive/Reactivate sources shows 401 error in source log

• What do you mean by Deactive/Reactivate? maybe is Enable/Disable the source not sure here
• I couldn't reproduce the issue maybe you saw the error because your token has expired?

I reached out Attio support regarding create-update-record action.

@jcortes Attio's support says we should use a different attribute to record_id to attempt creating the record, and instead use an attribute that could be used as identity such as email_address, this is what they said exactly:

its likely because you are trying to Assert with a record id. Record ID is something we set internally and cannot be updated. For context, Assert a person Record endpoint allows you to create or update a record using a unique attribute (e.g., email_addresses) to find existing People records - if a match is found, the record is updated and if no match is found, a new record is created. Record ID cannot be used as a matching attribute in this context as the value wouldn't exist prior to record creation. Would it be a viable option to assert the record using email as the unique identifier?

Can you try that and let us know if that made the trick?