|
Integration
|
Documentation
|
What you can do
- ETL data FROM and TO any relational and NoSQL database
- CDC data from the supported databases
- Execute SQL queries and scripts
|
Integration
Generic HTTP connector
Using generic HTTP connector you can create a custom connector for
practically any HTTP-based web service. If curl, Postman or SoapUI
can do it
Etlworks can do it
as well, only better.
Read
more
|
Documentation
|
What you can do
- ETL data FROM and TO any Web Service
- Copy response from the HTTP request to a file
- Send the content of the file as a payload for an HTTP endpoint
- Call HTTP endpoint, optionally send a user-defined payload to an
HTTP endpoint
|
Integration
Connectors for business apps
Etlworks includes hundreds of ready-to-use read/wrire
connectors for most
popular business apps and online data sources.
Read
more
|
Documentation
These are just a few exampes. There are many more connectors
|
What you can do
- ETL data FROM and TO any supported business app and online data
source
- Execute SQL queries and scripts
|
Integration
Connectors for file storage systems and data exchange formats
Etlworks supports HL7 2.x, HL7 FHIR, X12 and EDIFACT data exchange
formats, as well as more common CSV, XML, JSON, Excel, Parquet, Avro
and many other formats.
Read
more
Etlworks also supports most commonly used file storage systems such as
Amazon
S3, Azure Blob, FTP and many others.
Read
more
|
Documentation
|
What you can do
- Copy/Move/Rename/Delete/Archive/Split/Merge files in any of the
supported file storage systems
- ETL files FROM and TO any of the supported data exchange formats
- Send and receive EDI and HL7 messages
|
Integration
Connectors for message queues
Message queues, such as Kafka, can be used to build real-time data
pipelines to connect various applications. Etlworks supports most
well known messages queues.
Read more
|
Documentation
|
What you can do
- ETL data FROM and TO any message queues
- CDC data from the supported databases to message queues
|
Integration
Connectors for email systems
Etlworks can read emails and email attachments using the POP3 and
IMAP protocols and send emails using the SMTP protocol as well as
vendor-specific APIs such as Micsosoft Exchange, Office 365 and
Gmail.
Read more
|
Documentation
|
What you can do
- Send and receive emails and attachements
- ETL email messages and attachments to any destination
- Work with email messages in Microsoft Exchnage
- Work with email messages in Office 365
- Work with email messages in Gmail
|
Integration
User-defined API
A user-defined API allows the developer to create custom HTTP
endpoints,
that can receive requests from third-party applications, triggering
execution of the Flows in Etlworks.
Read
more
|
Documentation
|
What you can do
- Build HTTP endpoint to enrich data from multiple sources and expose
it to third-party apps
- Build HTTP endpoint that can ETL the payload sent from the
third-party apps
- Build HTTP endpoint for CRUD operations
- Build HTTP endpoint to upload files into any supported files storage
system
|
Integrations
Built-in APIs
Whether you want to build event-driven data integration Flows or
incorporate the Etlworks into your own automation workflow, you can
use built-in APIs to achieve your goals.
Read
more
|
Documentation
|
What you can do
- Create and manage flows, connectons, formats and schedules using API
- Execute and monitor flows
- Create reports
- Monitor health of the Etlworks instance
|
Integration
Webhooks
Webhooks allow you to set up integrations, which subscribe
to certain events in the Etlworks. When one of those events is
triggered, we'll send an HTTP POST or GET request to the Webhook's
configured URL.
Read
more
|
Documentation
|
What you can do
- Use Webhooks to update your external system about events happening
in the Etlworks
- Send notifications about events happening in the Etlworks to Slack
|
Company
Contact us
Resources
Back
Billing account
Documentation
Videos
Case studies
Partners
Feedback and
Roadmap
Blog
On-prem installers
Sign in