feat: submit pipefy-automations-formulas

[danielgualberto]

Skill

Folder / Pasta: submissions/danielgualberto/pipefy-automations-formulas/

What it does / O que faz: Native run_a_formula (Aplique uma fórmula) with field_map formulas and %{tokens} beyond get_automation_event_attributes (one official row today). Immediate on the card — not iPaaS. update_card_field only copies text; it does not evaluate SUM/IF.

Contact / Contato

Email: danielgualberto@live.com

Name for credit / Nome para crédito: Daniel Gualberto

The problem it solves / O problema que resolve

Same-card SUM/IF/weekday/SLA digest was routed to iPaaS or guessed from a one-row official token catalog.

What it built when you ran it / O que ela construiu quando você rodou

create_automation active=false with run_a_formula (SLA digest: WEEKDAY / INTERVAL_WEEKDAYS / CONCAT / assignees). get_automation round-trip. First attempt update_card_field was the wrong action and was deleted. See EVIDENCE.md.

What you had to fix / O que você teve que corrigir

update_card_field copies formula text instead of evaluating it. run_a_formula needs field_updated + camelCase triggerFieldIds. Live proof is the skill's SLA digest.

Checklist

• I provided a contact email in this description.
• I ran this skill in a real Pipefy organization.
• SKILL.md and EVIDENCE.md are both in the folder.
• The frontmatter name matches the folder name.
• No tokens, keys, real IDs, customer names, or personal data.
• I wrote this skill, and I agree it is published under Apache 2.0 with credit to me.

[adriannoes]

Thank you for taking part in MCP Builders, Daniel.

What we verified

We reproduced the steps on a fresh pipe and they worked on the first pass.

• create_automation accepted the payload with triggerFieldIds and field_map at active=false, and get_automation returned the formula intact.
• Enabling through extra_input worked. After a field update the destination held the computed digest, with nested IF, INTERVAL_WEEKDAYS, CONCAT and SUM all evaluated.
• The same formula sent through the update_card_field action landed as literal text with only the tokens substituted, which confirms the copy versus evaluate distinction the skill is built on.
• The snake_case trigger_field_ids rejection message matches the one quoted in the skill word for word.

The toolkit's automations skill covers update_card_field with field_map and a few tokens and says nothing about run_a_formula, its functions or its quoting rules. This skill fills that gap.

Changes requested

All text-only. The skill itself runs.

1. Remove the claim that run_a_formula rejects card_created. create_automation accepted that pair on a clean pipe. The action's eventsBlacklist lists only scheduler, and triggerEvents is the builder's suggestion list, not the compatibility gate. The claim appears in step 2, the success criteria, the failure-modes table and EVIDENCE.md.
2. In EVIDENCE.md, delete the template's "Keep this short" line and the note to self in the screenshot caption.
3. Fix the CLI example. As written it does not parse: the flags are --event-id (or --trigger-id), --action-id and --no-active, and the formula has to go through --extra with the event_params and action_params.field_map JSON. Without --extra the command creates a rule with no formula.
4. Drop or repoint the two See also links to skills that are not in the toolkit.

One smaller point: the SLA digest flags only WEEKDAY = 7, so a Sunday due date (WEEKDAY 1) is not treated as a weekend.

Next steps

The submission is accepted into the program. The changes above are about getting the text right before it is merged; push them to this branch and we merge. After that, we will bring the skill into the official Pipefy AI Toolkit repository, adapted to its format and CI, referencing this pull request and crediting you as a contributor there. We will reach out by email about the details.

[adriannoes]

CI update: the validate check is green on this branch. The changes requested above are text-only and do not depend on CI; once they land we merge.