# invokeETL

invokeETL() function is the Standard function available in 200OK.

**Description**  :  The fx\_etl function facilitates ETL (Extract, Transform, Load) operations with parameters including ETL API Name, Subtype, RecordId, and Custom JSON. RecordId and Custom JSON are optional. Subtypes like E (Extract), T (Transform), ET (Extract & Transform), TL (Transform & Load), and ETL (Default) determine the specific operation.

**Syntax** : fx\_etl(ETL\_API\_Name,Subtype,RecordId,CustomJSON)

**Example** : fx\_etl("Sales\_Extract","ET", "001G00000123456789",{"filter":"active"}) initiates an Extract & Transform operation for the 'Sales\_Extract' ETL API, using the specified RecordId '001G00000123456789' and Custom JSON data to filter active records.

Here we go with simple scenario using the above function.

**Scenario** : In a corporate data hub, analysts automate ETL tasks using fx\_etl to integrate sales data from diverse sources. With customizable parameters like Subtype and Custom JSON, they ensure seamless extraction, transformation, and loading processes for centralized analytics.

**ETL**<br>

<figure><img src="https://lh7-us.googleusercontent.com/swgG-4VFiQFwqGmvRJEOwqlwfkdgNnvRfaa-XwJS60njGBjJO75gRFa7EEGr24fz7ie9s5trBkpQNj0b2cVGN7tdgo4Npv-acAcrRAmTCe3Npb30xfk74zte9z6CmJyUjX_im9SlHrWsFOdng2FyWCc" alt=""><figcaption></figcaption></figure>

\
**Transform data**

<figure><img src="https://lh7-us.googleusercontent.com/gaZFWcfzwl6DJm0ojLWHgi7Z0mALyFjTyGjDNsyugnrytELiK5qk-xcE8vcx2_DMACw3a2RSxAzFNWcT8OCbGBE3v5w9J60PS5tbyxj78cruKzG371TaFawU6ZyTjkW9S-lZzCPgd4omwu3AdCF1SKg" alt=""><figcaption></figcaption></figure>

**Run the Channel**

<figure><img src="https://lh7-us.googleusercontent.com/JkwFIRbg1mBr2Dqo92LLv7fTaMiTVlF9Cwov1QP3SKDgLjPIuflxMrimh47WzhLrSiyXN6V5GUbh878EE9hqhuKKS5HpOHb6vmLy-r3xaRsXK7hTJcwpucfKBogmQJSYauc2sadCWxSAk5OiB_SPX48" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/NcXsozkL84lqqhgtE4OQqrkFuqnawaAZrrHB0PVUXAmnN1RMXfY_YYvBZM7MSwfYyjyPxhlZwECMZWNNYCKFXCDNAthbVsTGcKrfQA9JelP2kb15rnYqvb2vv7c7JJoY68f6iCe6oP4-E3ZVtVd-gsQ" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/Ao_MfHvLOAI70Xhqe-G5XSAduM98DzvcuJxRTr3cwmtgzZ2HplfN-rch2aUd9m_yN63QR3mV7Jrca3jzOjoyjjUtducGu2O74Pf5JDqpK2myaS107kPgnZaa_lZeLsutEpB_QPkFm8BynyLpZdDkkQE" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://200ok.gitbook.io/200ok-documents/user-manual/built-in-functions/advanced/invokeetl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.