Hi, I’m having an issue where Zapier is not getting triggered using the trigger “Object Created in Backendless” for one of my data tables.
Is this because the object is getting created via codeless and not API? It looks like I have not hit the API event handler limit.
Thank you
Hi Nikita,
Definitely, attached are screenshots of the Zapier workflow. Basically upon user registration my app also creates an entry on the “Profile” data table and is updated with user data. I want Zapier to pick up the new profile entry and create a contact with that information in Hubspot. It seems like the first step of the Zap is not getting triggered.
Hello @G1299
We will be happy to assist you. I need to ask you a few more questions so I can understand the problem better.
Please provide your Backendless applicationId.
The “Profile” data table in Backendless?
What application did you choose when configuring Zap?
Which table did you choose when setting up the Zap?
Test for trigger Object Created in Backendless is OK?
Test for Create Contact in HubSpot is OK?
Regards,
Vladimir
Hi Vladimir,
Application ID: B46B9599-0927-5212-FF01-2D3539543E00
The “Profile” data table in Backendless? - That is just the name of one of my app tables
Test for trigger Object Created in Backendless is OK? Yes
Test for Create Contact in HubSpot is OK? Yes
hello @G1299
there is an easy way to test integration. When you register trigger backendless creates non blocking event handler. So to see the result of execution of event handler you can change it to blocking:
and when I changed it, and saved the object with the rest console I got the following result
{
"attempt": "018a4f23-d004-ddc4-35f1-069df8160cd4",
"id": "018a4f23-d004-ddc4-35f1-069df8160cd4",
"request_id": "018a4f23-d004-ddc4-35f1-069df8160cd4",
"status": "success"
}
So backendless successfully sends the result of object creation to the zapier side.
Back to original question
Is this because the object is getting created via codeless and not API?
when you use server-side codeless or any other language, the event handler will not be triggered. Because server cloud code use CloudCode API key, if the call goes
CloudCode API key we do not execute backendless handlers. As workaround, you may create an object using a network block:
Got it, thank you for the explanation!
I’m now trying to figure out how to set a related object between “Users” and “Profile.” Now since we’re creating an object with HTTP/s, we’re not returning an objectId to set the relationship.
