FINANCE

FX hedge-shortfall detection with Asana follow-up tasks

Daily, compares net currency exposure from Snowflake against booked hedges and, for any currency where unhedged exposure exceeds tolerance.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily post-booking schedule fires
  • ActionQuery receivables and booked hedges per currencySnowflakeSnowflake
  • ActionConvert unhedged residual to base currencyHTTP webhook
  • LogicSelect currencies over hedge tolerance
  • OutputCreate hedge follow-up task on treasury boardAsanaAsana

What it does

Goes beyond raw exposure to surface the unhedged gap. It pulls open receivables per currency from Snowflake, subtracts booked hedge notional per currency, converts the residual to base currency, and identifies currencies whose unhedged amount exceeds tolerance. For each one it opens an Asana task — with the currency, shortfall amount, and suggested action — assigned to the treasury board so nothing falls through.

When to use it

Use this when the job isn't just measuring exposure but closing the loop on hedging — turning a daily gap analysis into concrete, trackable work items for the desk.

How it works

  1. 1A daily schedule trigger fires after hedge bookings settle.
  2. 2Snowflake returns open receivables and booked hedges per currency.
  3. 3An HTTP rate call converts the residual unhedged amount to base currency.
  4. 4A logic step selects currencies whose unhedged gap exceeds tolerance.
  5. 5An Asana task is created per flagged currency on the treasury board.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Connect AsanaTasks, projects, milestones — everywhere.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.