Database integration channel
The database integration channel is a way to integrate Auron Omni with an external database using either an existing table or a set of stored procedures.
Find more information about channels in general here.
Use the database integration channel to connect to any database that has ADO or ODBC drivers available. For example:
- Microsoft SQL Server
- PostgreSQL
- MySQL
- MariaDB
- Oracle
- And others
The database integration channel works with any message type, including SMS, WhatsApp, and email.
With the database integration channel you can send messages from an external data source and receive messages into an external data source. You can also update message status in your external database based on send and delivery status.
Edit database integration channel
You can connect to multiple external databases at the same time by creating multiple database integration channels.
Settings
| Property | Description |
| Connection string | This is an ADO or ODBC connection string that connects to your target external database. |
| Escape characters | Specify a list of characters that require an escape character before storing data in the external database. |
| Escape option | Specify how character escaping works. This can be either:
|
| String length | This is the maximum length for any string in the target database. If you are receiving data into the target database, message bodies are truncated at this length. |
| Select from | Select messages to send from the external database. This can be either a SELECT query from a table or a stored procedure call. |
| Confirm sending | (Optional) Confirm that a message is being sent by Auron Omni. This statement should update the status in your remote database to indicate that the message is being sent.
You can use fields from the remote database “Select from” query by enclosing them in % characters. For example, if your remote database has a key field called ID, you can use %ID% to refer to it. |
| Map message fields | Select which message type this channel sends and or receives.
Map fields from the “Confirm sending” statement to message fields in Auron Omni. The “Attachments” field is a special case. Auron Omni expects a field with semicolon separated file paths. Auron Omni must be able to access these files. |
| Receive message | (Optional) Specify how a message is stored in the external database. This can be an INSERT statement or a stored procedure call. Refer to Auron Omni message fields by enclosing them in % characters.
Specify an attachment directory for incoming attachments when applicable. If a message has attachments, the %ATTACHMENTS% field contains semicolon separated file paths. To receive files you must also set up a “Database Integrate Forward” trigger. This trigger forwards messages from any channel to the database integration channel. |
| Status update | (Optional) Specify statements to update the status in the remote database based on message status in Auron Omni.
To receive status updates you must also set up a “Database Integrate Status Update” trigger. This trigger updates message status in the database integration channel. |
| Poll interval | This poll interval applies to sending messages from a remote database. Receiving messages into the external database is always immediate. |
| Connection options | Define when the remote database connection is reset. This can be after every send or receive batch, or after a set number of minutes. You can also reset the connection automatically if an error occurs. On reset, the connection closes and reopens. This forces the database driver to reset. |
| On new record | Specify what happens with new messages. This can be:
|