Challenge 2 – Intermediate: “Chain Reaction”
Automate a multi-step process that spans multiple tools.
Challenge
Challenge 2 – Intermediate: “Chain Reaction”
Objective: Automate a multi-step process that spans multiple tools.
Requirements:
- Participants must utilize Unified Context Layer only - https://ucl.dev/. See the Unified Context Layer documentation here.
- Participants can use any other platform to build apps, automations, etc but they must call upon UCL
- Connect 2–3 tools (e.g., Trello + GitHub + Slack).
- When something happens in one tool, your flow should process it and take actions in others.
**What does this mean:** You’re setting up a trigger in Tool A that kicks off your agent to do useful work, and then push actions into Tool B or C. It’s a small automation, not just a single action.
**Typical flow:** 1. Trigger event occurs (e.g., new GitHub issue). 2. Agent reads data, summarizes/transforms it (e.g., extract priority, owner). 3. Agent creates/updates artifacts in other tools (e.g., Trello card, Slack alert). 4. Optional: write back status or a link to close the loop.
**Example ideas:** - A bug triaging bot that reads GitHub issues, summarizes them, and adds tasks to Trello. - A class project tracker that syncs deadlines and alerts teammates automatically.
**How to embed UCL:** [https://docs.fastn.ai/ucl-unified-context-layer/embedding-ucl-onto-your-ai-agent](https://mlh.link/ghwdata925-fastn-ucl-embed)
**How Unified Context Layer helps:** - Orchestrate across tools from one place. - Disable, enable actions without the need to map actions on the backend. - Utilize a single server URL or JSON to call upon tools.
**Submission checklist:** - Clear trigger in Tool A - Agent does some processing (not just copy-paste) - At least 1-2 actions in other tools - Demo shows the entire chain end-to-end - Submit a link to your code repository
Submissions are only open during the event.