Actions — What a Workflow Can Do
Table of contents:
- Feed operations (synchronization, rule change)
- Campaign operations (changing budget, bid, status)
- Task operations (creating, assigning)
- Sending notifications (email, webhook, Slack)
- Invoking an AI agent
- Summary of available action blocks
An action is the final block in a workflow sequence — it is what Sembot actually does after fetching data and evaluating conditions. A single workflow can contain multiple action blocks that execute in sequence.
Feed Operations (synchronization, rule change)
Direct actions on product feeds — catalog synchronization, changing transformation rules, or exporting to a platform — are not currently available as native workflow blocks.
Indirect workarounds:
- The HTTP Request block allows you to call an external feed management system via its API
- The AI Agent block can prepare data or recommendations regarding rules, which a specialist then applies manually
Campaign Operations (changing budget, bid, status)
Directly changing a campaign budget, CPC bid, or campaign/ad group status is not currently available as a native workflow block.
Indirect workarounds:
- The HTTP Request block allows you to call the Google Ads API or Microsoft Advertising API directly, provided you have an authorization token
- The AI Agent block can analyze data and identify which campaigns require changes — the result is delivered as a task or comment to a specialist
Task Operations (creating, assigning)
Tasks are the area where workflows have the greatest capabilities today. Two blocks are available:
Sembot Task — Create a Task
The workflow creates a new task in Sembot — fully configured, exactly as if a person had done it manually.
What you can set:
| Field | Description |
|---|---|
| Title | Task name — can include data fetched earlier in the workflow |
| Description | Detailed description — e.g., an automatically generated report from campaign data |
| Project | Which project the task will be assigned to |
| Priority | Low / Medium / High / Urgent |
| Status | New / In Progress / Completed / Cancelled |
| Assignee | Who is responsible for the task |
| Due Date | Deadline date |
| Section | Column on the Kanban board |
| Labels | Tags for categorization |
| Parent Task | If this is a subtask of an existing task |
Typical scenario: Campaign monitoring detects that CPC has risen by 30% — the workflow fetches the details, checks the condition, and automatically creates a task for a specialist with the title "Check CPC increase in Campaign X" and a description containing the current data.
📸 [SCREEN: "Sembot Task" block form — title, project, assignee, and due date fields]
Sembot Comment — Add a Comment to a Task
The workflow appends a comment to an existing task. The comment can include data fetched earlier in the workflow — such as the current campaign state, report results, or an AI agent's response.
Parameters:
- Task — specify which task should receive the comment
- Comment content — text that can dynamically include values from previous workflow blocks
Typical scenario: You have an open task related to a campaign. A workflow triggered every Monday fetches data from the past week and appends an up-to-date comment with the results to the task — no manual work required.
📸 [SCREEN: "Sembot Comment" block form — content field with visible dynamic variables from previous blocks]
Sending Notifications (email, webhook, Slack)
The HTTP Request block is a universal tool for sending notifications and communicating with external systems. If a system supports an API or webhooks, Sembot can send data to it.
What you can do:
- Slack notification — Slack provides Incoming Webhooks: paste the Slack webhook URL and Sembot will send a message to the selected channel
- Teams notification — same as Slack, via a Teams Incoming Webhook
- Email via external API — through services such as SendGrid or Mailgun (Sembot does not have native email sending)
- Your company's own API — if your company has an internal system, Sembot can call it
- Calling an external system — e.g., a CRM, advertising platform, or reporting tool
Configuration parameters:
| Field | Description |
|---|---|
| URL | Target address (API, webhook) |
| Method | GET, POST, PUT, PATCH, or DELETE |
| Headers | E.g., Content-Type: application/json |
| Request body | Data to send (JSON format) |
| Authorization | None / API key / Bearer token |
| Timeout | Maximum block execution time (in seconds) |
| Retry on error | Automatic retry on failure (max. 5 attempts) |
| Continue on error | Workflow does not stop if this block fails |
Example — Slack notification:
Method: POST
URL: https://hooks.slack.com/services/T00/B00/xxxxx
Body: {"text": "Campaign X has exceeded the daily budget!"}📸 [SCREEN: "HTTP Request" block form — URL, method, headers, body, and authorization fields]
Invoking an AI Agent
The AI Agent block runs a previously configured AI agent with a given question or command. This allows you to combine automatic data fetching with intelligent analysis or content generation.
Parameters:
| Field | Description |
|---|---|
| Agent | Select one of the previously configured AI agents |
| Prompt | Question or command for the agent — can include data from previous blocks |
| Project | Project context for the agent |
If you fetched campaign metrics from Google Ads earlier in the workflow, you can pass them to the agent as context and ask for an analysis, summary, or recommendation. The agent's response can then be added as a comment to a task (Sembot Comment) or sent via HTTP Request to another system.
Typical scenario:
[Get data — Google Ads]
↓
[AI Agent: "Analyze the results and identify campaigns that need optimization"]
↓
[Sembot Task — create a task with the agent's response as the description]For details on configuring AI agents, see Chapter 11.7.
📸 [SCREEN: "AI Agent" block form — agent selection from list, prompt field with dynamic variables]
Summary of Available Action Blocks
| Block | Available | Typical Use |
|---|---|---|
| Feed synchronization | ❌ Not available | Possible indirectly via HTTP Request |
| Change campaign budget / bid | ❌ Not available | Possible indirectly via HTTP Request (Google Ads API) |
| Sembot Task | ✅ Available | Automatically creating tasks for the team |
| Sembot Comment | ✅ Available | Recurring status updates on tasks |
| HTTP Request | ✅ Available | Slack, Teams, email via API, external integrations |
| AI Agent | ✅ Available | Data analysis, content generation, recommendations |