Topics started by savicbo

4 Topics

savicbo
savicboInspiring

Improved notification for unread emailsSubmitted

Currently the best way to be notified when a card receives an email is if you are assigned to that card. However if your process is managed by a team there’s no great way to flag a new email having come in to a card especially when there are many cards. In theory we could use the “when an email is received” automation trigger BUT that requires you select a phase. When a process has many phases this is hugely impractical. Therefore the suggestion is two fold: Short term: Allow the “when an email is received” automation to not require a phase Long term: Create a way for an entire team to easily identify any unread emails. Maybe a pipe can have an inbox of all the emails any card in the pipe receives? Not sure the best solution but maybe we can share ideas below?

5
lucas-fernandes4
2 years ago
savicbo
savicboInspiring

Email whitelistSubmitted

The ability to accept only specific email domains in an email field. For example, if I work for Acme Inc. and make a form for my employees, I want to require that the email field have @acme.com in it. This will avoid employees submitting requests from their personal email address by accident or someone from outside the company submitting requests. Logistically, this could be as simple as an option that can be enabled when adding the field. When enabled the user can enter a list of domains that are acceptable (would be important to allow more than just one domain). Edit: there is a hacky way to do this with conditionals by showing text warnings / hiding fields but it leads to very quirky user experience and people submitting empty requests

1
Giovanni Basso
Pipefy Staff
3 years ago
savicbo
savicboInspiring

Product RoadmapReleased

We’ve heard that there’s so much exiting work being done by the Pipefy team and it would be great to have a place community users could see the current Pipefy product roadmap. One good example is Front’s public roadmap. 

2
savicbo
3 years ago
savicbo
savicboInspiring

Improved Slack IntegrationSubmitted

The current Pipefy<>Slack integration is a good chat but is very limited in capability. With ChatOps becoming increasingly popular, I think Pipefy has a great opportunity to take advantage. There are a few different integration options I have in mind: Integration with Slack users. Not only for login but moreso to replace email notifications. Many startups and even large organizations like ours are using email very sparingly favoring Slack instead. This would make it easier for a requester to receive emails regarding their request. Communication. It’d be great to be able to communicate with a requester or even others managing a pipe through Slack. For example, a new card could open a channel which then displays in the card.  Actions through Slack. Wouldn’t it be great if we could type “/pipefy request a new unicorn” in Slack and within my Slack window fill out the start form for the “new unicorn” pipe? Similarly if a request requires approval from an executive it would be so mu

0
savicbo
3 years ago

Community Experts Leaderboard

Terms & ConditionsCookie settings