# Using external DB events to drive workflows in temporal

**URL:** <https://community.temporal.io/t/using-external-db-events-to-drive-workflows-in-temporal/13363>\
**Category:** Community Support\
**Tags:** general-impl\
**Created:** [September 1, 2024, 8:17pm UTC](https://community.temporal.io/t/using-external-db-events-to-drive-workflows-in-temporal/13363 "2024-09-01T20:17:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [September 2, 2024, 12:55am UTC](https://community.temporal.io/t/using-external-db-events-to-drive-workflows-in-temporal/13363/2 "2024-09-02T00:55:35Z")

</div>

It looks like you are implementing the [transactional outbox pattern](https://microservices.io/patterns/data/transactional-outbox.html) for your DB. In this case, I would create a consumer process that reads messages and routes them to the appropriate workflow in the form of signals. Consider using signalWithStart to crate workflows lazily.

---

_[View the full topic](https://community.temporal.io/t/using-external-db-events-to-drive-workflows-in-temporal/13363)._
