Connector Improvement: Iterable Journeys (Workflows)
AnsweredAs of now, it is quite impossible to get workflow metadata from iterable, apart from the Workflow_name. Also, this only happens if a subscriber performed any event.
We would like to have the following endpoint, so that we have information for every single existing workflow.
-
Official comment
Hi Héber,
Thank you for sharing your feature request with us. To ensure we fully understand and address your needs, could you please provide a bit more detail?
We already use the webhooks you linked to to populate the EVENT_EXTENSION table in our schema. That table includes workflow_name and workflow_id. Those two fields are the only fields mentioned in the endpoint documentation you provided. What additional fields are you looking for, and do you know where we can retrieve them?We appreciate your engagement and look forward to your clarification.
Best,
Luke -
Hey Lucas,
The reason why I ask is because not every workflow in Iterable is meant to execute a marketing action. For example: Sometimes a workflow is created just to split audiences or only update contact values. Those workflows are also important for further analysis and cross-references with internal data.Since they don't trigger any of the classic events, they never show up on the events endpoint.
-
Hello,
Iterable Journey table/data is not yet enabled via Fivetran today, would like to get it enabled at the earliest.
Business Use Case: Campaign/Journey data is widely used in Snowflake for analytics and reporting, particularly for building leadership reports.
Impact: Currently, there is no equivalent table available in Snowflake to retrieve Journey data. To enable reporting, we require the Journey table/data to be integrated into Snowflake via Fivetran.
Urgency: This is a high-impact requirement since there is no alternate object available. We request that the Journey object be enabled at the earliest.
Thanks!Rakesh
Please sign in to leave a comment.
Comments
3 comments