I have 3 zaps being triggered by Close.com New Note, New Call and New Email triggers.
These workflows were running successfully. However, a few days ago they started to repeatedly fire(as if looping), obviously resulting in repeated posts in the target service data.
This repeat firing occurs until the zap is turned off. There are no errors reported in Task history.
Has anyone experience something similar?
Your assistance to resolve this issue is greatly appreciated.
Best answer
Repeated firing of Close.com tiggers
Best answer by amarunda
Utilised Python code as follows. I have excluded the header and url
root[0] is the key to getting the 1 response i.e the first record
import requests
from xml.etree import ElementTree
from base64 import b64encode
headers = XXXXXX
url = XXXXXX
response = requests.get(url, headers=headers)
response.raise_for_status()
root = ElementTree.fromstring(response.text).findall('person')
if len(root):
print(ElementTree.tostring(root[0], encoding='unicode').replace('\n','').strip())
return [
{field.tag: field.text for field in root[0]}
]
else:
return {'id': 'not found'}
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.


