-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webhook verified source #510
Comments
Hey @alberto-lanfranco-storebrand, thanks for the suggestion. Could you describe your use case in more detail? |
Hi @burnash ! Thank you for your prompt response, and sorry for the delay in my reply. Here is a detailed description of our use case: Project OverviewWe are a data engineering team working on a project to integrate data from a SaaS tool into our data platform. We aim to switch to a direct integration using the tool's webhook interface to receive real-time updates. Integration RequirementsThe SaaS tool sends JSON payloads via HTTP POST requests to a specified endpoint whenever there is a change in the system. Key requirements include:
Proposed SolutionWe envision a solution where dlt can:
ConclusionIn summary, integrating webhook support into dlt would significantly streamline our data ingestion process, allowing us to leverage real-time updates while maintaining cost efficiency and data freshness. We believe this feature would not only benefit our use case but also enhance dlt’s capabilities for other users with similar needs. Thank you for considering our request, and we look forward to your response. |
Hi @alberto-lanfranco-storebrand thanks for the details. Just to recap: you would like to have some endpoint which when triggered by SaaS tool receives the payload and calls dlt to do the ingestion. Is it his correct? |
In our case the code would run either in an AKS cluster (together with dlt and dagter) or in Azure Container Apps |
It would be very useful for us to use dlt to ingest data that is delivered from a webhook.
Is this something that dlt could officially support?
The text was updated successfully, but these errors were encountered: