Contact table
Answered
Connector name: Lemlist (lite)
Table name: Contact
API documentation link:
Additional details: we now only receive the leads, but not the contacts that are not actively pursued via a campaign
-
Official comment
Hi Mats,
Thank you for the request.
We have added a contact table to our active backlog for the Lemlist connector, and we have confirmed the API provides a contacts endpoint for this. To help us scope it, could you tell us which contact fields matter most to you and roughly how many contacts are not attached to a campaign today? We will keep you updated on this thread as we make progress.
Best,
Syead Mujtaba Imam Rizwi -
Thank you for the follow-up.We are looking most specifically for the creation date of the lead, but we cannot find it in the lead table. We could then look at the contact level, but after discussion we concluded that this is sub-optimal, as a contact can be connected to a campaign multiple time. Unfortunately, we do not see the creation date on the lead (combination of contact and campaign), so we will request Lemlist to add this to their API. For now, we would like to have the creation date of the contact as well, to determine pipeline staging.Can you also add more details to the campaign table? Lemlist Developer Docs. We would like to see the senders' objects on the campaign entity, so that we can assign the leads to sales reps in Databricks.
-
Hi Syead,
We've received the message from Lemlist that the lead creation date will be added to the lead entity. So it would be great if that property is also added to the Fivetran - Lemlist connector.
'The team confirmed that the API change to include the lead creation date in the lead related responses will be live next Monday.'
Please sign in to leave a comment.
Comments
3 comments