No account needed: go from product data to a task about its visibility.
Example workspace
Advertising
Google AdsFacebook AdsMicrosoft AdsChatGPT AdsTikTokComing soonInstagramPinterestComing soon
E-commerce
ShopifyWooCommerceMerchant Center
Team
AsanaClickUpComing soon
Event → Process → Task → Action
Reads and actions follow the connection’s permissions.
Sample data
EXAMPLE WORKFLOW
Connect a source to a specific task.
Example: a change in product availability calls for a review of its exposure. Choose the relevant sources and objects, then check the full workflow. Connecting an account is the starting point for working with its data.
01
Identify the question and source.
Choose the product, campaign or team task to monitor. Select an integration with the required data and confirm access. Catalogue data and advertising results may come from different accounts and need to be linked.
Step outcomeA chosen object and the required data scope.
02
Check the data in a process.
During setup, verify the account, object identifiers and data freshness. Run the process for the agreed scope. Missing data or permissions need to be understood before deciding whether a situation needs intervention.
Step outcomeA process result with clear source context.
03
Move to an available response.
Open the task and review the related data. Work in an available Sembot view, follow a source link or use an action supported by the integration. Choose notification channels separately for the responsible person and the importance of the issue.
Step outcomeA task that leads to the right place to act.
01
MARKETING
Connect campaigns with their results.
Work with channels such as Google Ads, Facebook Ads, Microsoft Ads, TikTok, Instagram and Pinterest. Data access and actions depend on the integration and account permissions.
Advertising accounts and objects
Results and events
Scope shown when connecting
02
E-COMMERCE
Add catalogue and store context.
Shopify, WooCommerce and Merchant Center help connect a product with its price, availability and exposure. Choose the source required by the process.
Products, prices and availability
Feed data
Source quality and freshness
03
TEAM
Bring team tools into the same flow.
A task from Asana or ClickUp can signal more work. Email, SMS and Twilio calls let you deliver notifications through the appropriate channel.
Asana and ClickUp
Notifications and actions
Access and rules set during configuration
CHOOSE HOW TO WORK
What to check for every connection.
01
Reading and acting have separate scopes.
An integration may provide data to a process, while changes depend on the specific operation and permissions. Review the available operations for the tool you intend to use. Check support for the intended action and object before automating.
02
Match products to the right context.
Linking catalogue data with exposure requires consistent source information. Check product identifiers, the destination account and data freshness. This helps the team understand which product a task concerns and where to find a solution.
03
Notifications need their own setup.
Email, SMS and Twilio calls serve a different purpose from reading advertising statistics. Define recipients, required connections and notification trigger conditions. Availability and costs also depend on the chosen channel’s provider.
BEFORE YOU START
Good to know.
Do all listed platforms support the same actions?
No. Data, triggers and operations depend on each integration and account permissions. Confirm the scope required by your chosen process or action for the tool you use.
Can an Asana or ClickUp task start further work?
Yes, a task can act as a signal for a subsequent workflow. Match the connection and rule to the particular event, then define who receives the result and what should happen next.
How many integrations should I start with?
Start with those needed for your first process. A tested scenario with a clear result lets you assess the value of the connection before adding further sources and projects.