CRM and work

For: a contact form that lands in the CRM, and team screens over contacts, companies, deals and tickets.

Connects with: Connect with HubSpot, or a service key (starts pat-) made in HubSpot under Development, Keys, Service keys, with read and write for contacts, companies, deals and tickets. The full steps are in HubSpot.

Ask for:

• "Add an enquiry form that saves each person to HubSpot as a contact"
• "Let customers send a support request that becomes a HubSpot ticket"
• "Make a staff page with our open deals by stage"

Switches: Read and Change for contacts, companies, deals, tickets and notes.

Limits: visitors can create a contact or a ticket. Everything else is for your team only. Apps use HubSpot's own internal property names, and a deal stage is one of your pipeline's own, never made up. An app can read and change records, not delete them.

For: a contact form that becomes a lead in your pipeline, and team screens over deals, persons, organisations and activities.

Connects with: Connect with Pipedrive, or keys.

• Company domain: the part before .pipedrive.com in your address.
• API token: in Pipedrive, click your avatar, then Personal preferences, then API.

Neither is needed with the button.

Ask for:

• "Add a contact form that creates a person and a lead in Pipedrive"
• "Show a pipeline board with my deals by stage"
• "Let my team move a deal to the next stage"

Switches: Read and Change for leads, persons, organisations, deals, activities, notes, pipelines and stages.

Limits: visitors can create a lead or a person. Everything else is for your team only. An app can read, add and update, and cannot delete. Emails and phone numbers on a person are lists, as Pipedrive keeps them.

For: a contact form that lands as a lead, and team screens over leads, contacts, accounts, deals and tasks.

Connects with: the Connect with Zoho button. There are no keys to copy.

Ask for:

• "Add an enquiry form that creates a lead in Zoho CRM"
• "Make a team page with open deals by stage"
• "Find a contact by email on the team page"

Switches: Read and Change for leads, contacts, accounts, deals and tasks.

Limits: visitors can create a lead. Everything else is for your team only. An app can read, add and update, and cannot delete. Stage names are your own picklist values, read from your account.

For: invoicing inside a team tool: customers, unpaid invoices, estimates, payments received, and a new invoice from a form.

Connects with: the Connect with Zoho button. Apps use your Books organisation.

Ask for:

• "Show my unpaid and overdue invoices on a team page"
• "Add a form for the team to create an invoice for a customer"
• "List my customers and what each owes"

Switches: Read and Change for contacts, invoices, estimates, payments and items.

Limits: your team only, with no public side. An app can read and create, and cannot delete. Amounts are in your organisation's currency.

For: a contact form that becomes a Lead, a support form that opens a Case, and team screens over contacts, accounts and opportunities.

Connects with: the Connect with Salesforce button. Before the first connection, your Salesforce admin installs Setherion's package once, for all users: the card has an Install the Setherion package link. It adds no objects or code. It only lets your org sign in to Setherion.

Ask for:

• "Add an enquiry form that creates a lead in Salesforce"
• "Add a support form that opens a case"
• "Make a team page with open opportunities by stage"

Switches: Read and Change for leads, contacts, accounts, opportunities and cases. A Read switch also covers a SOQL query that names that object, so a query cannot walk around it.

Limits: visitors can create a Lead or a Case. Everything else is for your team only. A lead needs a last name and a company. An app can read, add and update, and cannot delete.

For: issue tracking in a team tool: list and filter issues, create one from a form, read teams, projects and cycles, move an issue along.

Connects with: Connect with Linear, or a Personal API key (starts lin_api_): in Linear, Settings, then Security & access, then Personal API keys.

Ask for:

• "Show the 20 newest issues on a team page"
• "Add a bug report form that creates a Linear issue"
• "Let my team move an issue to In Progress"

Switches: one pair for issues, projects and teams together. Read is looking, Change is creating, updating and moving.

Limits: your team only, with no public side.

For: a team's tasks inside an app: list a project's tasks, create and complete tasks, read projects and sections.

Connects with: Connect with Asana, or a Personal access token: in Asana, My settings, then Apps, then Developer apps, then Personal access tokens. Optionally add a Default project ID, the long number in the project's address.

Ask for:

• "Show the open tasks of my project on a team page"
• "Add a form for the team to create a task"
• "Add a Complete button on each task"

Switches: Read and Change for tasks, projects, sections, tags, comments and workspaces. Change includes deleting.

Limits: your team only, with no public side.

For: team screens over Jira issues and Confluence pages: open issues by project or status, an issue created from a form, issues commented on and moved along, and pages read, searched and written.

Connects with: Connect with Atlassian: sign in, choose your site, and allow Jira issues and Confluence pages. Or keys.

• Site: your Jira or Confluence address, like your-team.atlassian.net.
• Email: of the Atlassian account that made the token.
• API token: at Atlassian's API tokens page, choose Create API token, the one without scopes.

Ask for:

• "Show open issues in project WEB by status"
• "Add a form that creates a Jira issue"
• "Show the pages of my Confluence space, with search"

Switches: Read Jira issues, Create and change Jira issues, Read Confluence pages, Create and change Confluence pages.

Limits: your team only. Nothing is ever deleted. An issue changes status only through its allowed moves, as Jira requires.

For: letting visitors book a meeting with a real scheduling widget, and showing your upcoming meetings.

Connects with: your Calendly link, copied from your Calendly event page, or the Connect with Calendly button, which fills the link in for you. The widget needs only the link: no key, no sign-in, and it is public by design.

Ask for:

• "Let visitors book a call on the contact page"
• "Show my upcoming meetings on a team page" (only after you connect with the button)

Limits: the widget does the booking, so the app does not build its own calendar. Through the button, apps can only read your meetings, and who is coming to them is for your team only. Nothing can cancel or change one, so do that in Calendly. Test connection needs the button first, because it reads your bookings.

For: a booking page that offers only your free times and puts each booking on a calendar of its own.

Connects with: the Connect with Google button. You allow two things: a calendar named "Setherion bookings" that the app makes and writes to, and your free or busy times. Your own events are never read.

Ask for:

• "Let visitors book a 30 minute slot when I am free"
• "Show the bookings made on a team page"
• "Let my team cancel a booking"

Switches: Read bookings, Add, move and cancel bookings, See when you are busy.

Limits: visitors can see when you are busy, never what, and can book. Listing the bookings is for your team only. A booking invites nobody, so the visitor's details go into the booking text. The app checks your busy times before it books, because the calendar does not refuse overlaps itself.

For: a team screen over what people submitted to your Tally forms.

Connects with: an API key (starts tly-) from Tally under Settings, then API keys, and an optional Default form ID, the id at the end of the form's share link.

Ask for:

• "Show the latest submissions of my feedback form on a team page"
• "Show each answer next to its question"

Switches: Read forms and Read submissions.

Limits: read only: apps can never change Tally, and only your team can read the answers. To let visitors fill in a form, embed it in the page. That needs no key.

For: anything you have built as an n8n workflow: send a form on, look something up, start a job.

Connects with: your Webhook address, which is your n8n address up to and including /webhook, as the Webhook node shows it. Optional extras:

• Auth header name and Auth header value, if the Webhook node uses Header Auth. The value stays on Setherion's servers.
• A webhook path to test, the path of one active workflow's Webhook node set to GET, so Test connection can call it.

Ask for:

• "Send the contact form to my n8n workflow at contact-form"
• "Show prices from my n8n workflow at prices"

Limits: use the Production URL. A test address answers only once, after Execute workflow, and is refused when you save. A 404 means no active workflow listens on that path, so activate the workflow. An app can call any path under the address, with GET or POST, and the workflow decides what comes back.