Describe the chore. Get the workflow. Kovca turns repetitive ops work into workflows that run on new emails, tickets and messages, with approvals built in.
@nava_who_codes Good luck wrapping up the SFTP changes. Today I'm on Kovca, where a sentence like "when a Shopify product goes out of stock, message the team in Slack" becomes a running workflow.
@ehoneahobed This week I'm on Kovca. You type a chore like "when someone opens a GitHub issue, post it in our Slack channel" and it turns into a workflow that keeps running.
@navaneeth_pk If the headers show dkim=pass signed by https://t.co/ica4MhUFU9, that points to a compromised mailbox, since a spoofer can't produce their DKIM signature.
@YourAKShaw Fair suggestion, and thanks for pushing on it. I can't say whether that changes, but for now checking the provider's sent log before retrying a failed email step is the safe move.
@nickfrosty Kovca, a workflow builder. You write something like "when a new Jira ticket comes in, post it in our support Slack channel" and it keeps running as a workflow. Why: chores like that tend to stay manual because wiring them up feels like a whole project.
@YourAKShaw Not as a separate state. A step ends up as succeeded or failed, so a timeout after the provider accepted the email would still show as failed, with the error and any HTTP status attached.
@BertrandDiouly Shipping more of Kovca this week. You write a chore like "when a new Linear issue comes in, add it to our Google Sheet and post it in Slack" and it runs as a workflow after that. One micro-app every 10 days is a fast pace.
@YourAKShaw Fair, ordering narrows it rather than closing it. I can't speak to plans, but today the run view shows which steps finished, so someone can check whether the email went out before choosing to retry.
@sivunigunta@no_fear_inc Thanks, that answers it. The weekly review of misses you mentioned seems like what keeps a written rule like that from quietly slipping.
@SandrineZambou Thanks, that's a fair read. For support and ops folks the plain examples should come before the CLI and API, so I'll look at moving those down.
@aiwithadb Next week is more Kovca: you type something like "when a Slack message in our support channel mentions a bug, open a GitHub issue" and it becomes a workflow that keeps running. Happy to hear if that reads clearly.
@_josehelps Stripping HTML comments from the issue body before a bot reads it seems like a cheap first step, since the maintainer never sees that text anyway. It wouldn't cover other hidden text, so the no-secrets advice still matters more.
@YourAKShaw Nothing I can promise there yet. For now it helps to put a one-way step like sending an email last, so a run that fails earlier never reached it and a retry won't send it twice.
@alvetes17 SaaS side here: https://t.co/mzljj1u9AL. Kovca takes a request like "when a new Jira issue is created, post a summary in our Slack channel" and sets it up as a workflow that keeps running.
@YourAKShaw Honest answer: it doesn't hide all of it. Each run shows step by step where it stopped, with the error and HTTP attempts, and retrying an event runs its actions again, so a step like sending an email can repeat.
@Peteriishak Link's here: https://t.co/mzljj1u9AL. It's a workflow builder: you write something like "when a GitHub issue is opened in our repo, add it to Notion and ping Slack" and it keeps doing that on its own.