> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/tutorials/workflow-builder-tutorial/4.-types-of-workflows.md). # 📦⚡4. Types of Workflows ### 📦 Batch Workflow In our examples, we have so far seen how one time synchronization happens by clicking on Sync Now. In a real time scenario, Batch Workflows are usually used when you want synchronization to happen at regular intervals. Batch synchronization means data is updated in groups, not instantly. Think of it like doing household chores once a day instead of cleaning after every small mess. Scheduled Batch Synchronization runs automatically at fixed times, without any user action. It is suitable when: * Large amounts of data need to be updated * Immediate updates are not required * Data must be updated at a preferred time (for example, 12:00 AM UTC) or at regular intervals (such as every hour or every Thursday at 7:00 PM IST) Click on Workflows icon on the left side and you will see the list of workflows added in the Project. You will see the Schedule Manager in that.
Click on the Manage Button and Click on Add Schedule.
You can configure the frequency of when the sync needs to happen * Minute * Every \_\_ minutes: Use when you want the sync to happen at a frequency say, for example, every 5 minutes or every 30 minutes (You can configure the number till 60) * Specific Minute: Use when you want the sync to happen at a specific minute of the hour Example: Every 15th and 33rd minute of the hour. * Hour * Every hour: Choose when every hour when you want the sync to happen every hour (at the configured minute(s) if applicable) * Every \_\_\_ hour: Choose when you expect the sync at a frequency * Specific hours: Use when you want the sync to happen at a specific hours * Every hours between \_\_\_ and \_\_\_\_ : Comes in handy when you want syncs only during your working hours every hour * The same flexibility applies to the following options: * Every day, Specific day of week (choose one or many), Specific day of month (choose one or many) under day of the month * Every month, Specific month (choose one or many), Every month between \_\_\_\_ and \_\_\_\_\_ under Month etc.,
When you configure, you will see the description which helps you understand the configuration set. You can add schedules based on your use case. Auto Pilot Mode ensures the workflow runs automatically on the configured schedule without any manual intervention. Enable Auto Pilot Mode on. Once saved, you can see all your configured schedules listed under the Schedule Manager. On the workflow listing page, you can see when the next sync will run and when the previous sync has happened. You can check the logs from the Logs Icon for clarity. #### ⚡ Dynamic Workflow Dynamic synchronization means data moves immediately when something happens. You can think of it like a live phone call — you ask a question and you get an answer immediately, with no waiting. Dynamic Synchronization is “do it now”. When an action happens, the system uses an API request to inform the DCKAP Integrator. The dynamic workflow starts at once, processes the data, and sends back the response immediately. #### When to use Dynamic Synchronization? * When speed is critical * When real-time accuracy is required * When users expect instant updates Now let's build one and see it in action **Step 1:** Let’s create a dynamic Workflow. **Step 2:** Add Sample Data. Provide a sample of what the request body will look like when you call this workflow (In Dynamic Payload). This is essential for DCKAP Integrator to understand the structure to show in the Data Hub. Example: ``` [ { "price": 100, "type": "regular" } ] ``` **Step 3:** Add Code Runner to reduce $20 if the type is a “new” customer. ``` result = inputs["payload"] for i in result: if i["type"] == "new": i["price"] = i["price"] -20 response = result ``` Enable show in console logs for the step **Step 4:** Add Set Response Step as the last step - return the data you want to send to the caller which is Code Runner’s response. So, choose the Code Runner step result from DataHub. **Step 5:** After building the workflow, enable the console for the workflow and save. You can copy the URL using the Copy URL Button and use it anywhere. **Step 6:** Go to Postman. Add a Request and paste the copied URL. **Step 7:** Go to DCKAP Integrator -> Project Settings -> Access Key -> Click on Create New Key. Name the key and save. Copy the API Key. **Step 8:** Go back to Postman. 1. Go to the headers of the created request and add “Authorization” and in value type “Bearer ”and paste the key . | Authorization | Bearer \ | | ------------- | ------------------------ | 2. Keep the method as POST for the request 3. In Body, Raw, paste ``` [ { "price": 100, "type": "regular" }, { "price": 100, "type": "new" }, { "price": 243, "type": "new" } ] ``` 4. Hit Send. Check the result in Postman and see the Console Logs of your Dynamic Workflow. #### 🎉 Good Job! You executed your first Dynamic Workflow. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.dckapintegrator.com/tutorials/workflow-builder-tutorial/4.-types-of-workflows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.