Integration
Connect MagicBlocks to SLF
When something happens in MagicBlocks, your agent does the next thing in SLF. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want MagicBlocks and SLF to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with MagicBlocks and SLF
Triggers and actions 1 trigger · 6 actions
Trigger
Contact Created or UpdatedTriggers when a contact is created or updated.
- Create Contact
Creates a contact in your workspace
- Find Contact
Finds a contact by id or email or phone from your workspace
- Get Contact
Get a single contact by id, email, or phone. GET /v1/contacts/{contactId}, /v1/contacts/email/{email}, /v1/contacts/phone/{phone}
- List Contacts
List all contacts in a MagicBlocks workspace. GET /v1/contacts
- Update Contact
Updates a contact in your workspace.
Action
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.